-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Determine which turn-up guides can be replaced with kubeadm #1659
Comments
Woot |
@pwittrock do you wanna discuss this? |
@errordeveloper Yeah. Slack? Zoom? |
@pwittrock, was there any decisions made about this issue? |
@kubernetes/sig-cluster-lifecycle-misc Ideas? |
|
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
/remove-lifecycle stale SIG Cluster Lifecycle is looking into reprioritizing this in 2018 |
cc @kubernetes/sig-cluster-lifecycle-feature-requests |
You added the stale label btw |
@chrislovecnm Sorry, I don't understand your comment? |
I've just cross posted on the mailing lists about this: https://groups.google.com/d/msg/kubernetes-sig-docs/GFnX8DRw7iY/8y3feBK5AAAJ. |
Thanks IIya. It would be great if we could reach out to owners directly for any getting started guides (where we know them) in case folks are filtering the mailing lists in their email. Also, it might be nice to provide a link in the email to the list of guides that we are talking about culling. |
Now tracked in #7278. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
This is a...
Problem:
There are many outdated pages that do various flavours of cluster turnup.
Proposed Solution:
Redirect to kubeadm http://kubernetes.io/docs/getting-started-guides/kubeadm/.
The text was updated successfully, but these errors were encountered: