Skip to content

Instantly share code, notes, and snippets.

@krisnova

krisnova/kops-kubicorn-proposal.md

Last active November 8, 2017 16:22
Show Gist options
  • Save krisnova/c5f46d50e420e12d98d8c45d56b454b3 to your computer and use it in GitHub Desktop.
Save krisnova/c5f46d50e420e12d98d8c45d56b454b3 to your computer and use it in GitHub Desktop.
Download ZIP
Proposal for migrating kops and kubicorn into a new GitHub organization.
Raw
kops-kubicorn-proposal.md

Migrating Kops and Kubicorn into a new organization

Problems

  • We are fragmenting to the community (again) by offering kops and kubicorn at the same time.
  • We have learned a lot of lessons via each project, and would like a chance to start fresh with the new machine API.
  • We have a lot of small components lumped into monolithic repositories.

Solution

  • Cherry pick our preferred solutions from each of the projects into a larger (and new) GitHub organization.
  • Each of the smaller components will live in the new organization, as small, individual repositories.
  • We can bring in other projects, as smaller componenets of the organization.
  • We can start to break out the projects and combine them into new repositories in the organization.

The Organization

  • Will be community driven, and as "kubernetes official" as possible.
  • Will be Apache 2 licensed
  • Will implement the Kubernetes "official" Machine API, and possibly the Cluster API.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment