-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Labels
Comments
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. |
(1) seems quite reasonable to me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
/docs/getting-started-guides/coreos/
, link to the guides on coreos.com and explain options for platforms, etc.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).Any other ideas or preferences?
cc CoreOS folks: @aaronlevy, @bcwaldon
cc past contributors to docs: @pires, @vallard
The text was updated successfully, but these errors were encountered: