Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plan for maintaining CoreOS getting started #14205

Closed
robszumski opened this issue Sep 18, 2015 · 4 comments
Closed

Plan for maintaining CoreOS getting started #14205

robszumski opened this issue Sep 18, 2015 · 4 comments

Comments

@robszumski
Copy link
Contributor

CoreOS recently released coreos-kubernetes (blog post), which is a maintained set of guides and Vagrant examples for running single and multi-node Kubernetes clusters.

I wanted to start a discussion on how we (CoreOS) can best incorporate these guides into upstream Kubernetes. Brainstorming a few options to get the converstation started, from most to least ideal:

  1. Within /docs/getting-started-guides/coreos/, link to the guides on coreos.com and explain options for platforms, etc.
  2. Sync coreos-kubernetes guides into Kubernetes as they are updated. This means they get included in the release tarball and will appear on kubernetes.io (example).
  3. Maintain the existing guides as is and additionally mention the new guides
  4. Remove CoreOS guides completely from the getting started docs

Any other ideas or preferences?

cc CoreOS folks: @aaronlevy, @bcwaldon
cc past contributors to docs: @pires, @vallard

@pires
Copy link
Contributor

pires commented Sep 19, 2015

I believe it makes sense for you guys to maintain this. After all, you're CoreOS! But, I'm against removing all previous stuff, unless you provide equivalent support, namely for AWS, GCE and Azure.

@pires
Copy link
Contributor

pires commented Sep 19, 2015

Refs #9178 #14032

@davidopp
Copy link
Member

(1) seems quite reasonable to me.

@robszumski
Copy link
Contributor Author

I'll start working on a PR for 1. This should fix everything in #9178 #14032 other than the AWS issues, which I believe are being worked on separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants