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

Determine which turn-up guides can be replaced with kubeadm #1659

Closed
1 of 2 tasks
errordeveloper opened this issue Nov 10, 2016 · 19 comments
Closed
1 of 2 tasks

Determine which turn-up guides can be replaced with kubeadm #1659

errordeveloper opened this issue Nov 10, 2016 · 19 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.

Comments

@errordeveloper
Copy link
Member

This is a...

  • Feature Request
  • Bug Report

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/.

@errordeveloper
Copy link
Member Author

errordeveloper commented Nov 10, 2016

cc @pwittrock @jaredbhatti

@pwittrock
Copy link
Member

Woot

@errordeveloper
Copy link
Member Author

@pwittrock do you wanna discuss this?

@pwittrock
Copy link
Member

@errordeveloper Yeah. Slack? Zoom?

@a-mccarthy
Copy link
Contributor

@pwittrock, was there any decisions made about this issue?

@pwittrock
Copy link
Member

@kubernetes/sig-cluster-lifecycle-misc Ideas?

@colemickens
Copy link
Contributor

kubeadm directly (with manual IaaS provisioning?) or something like kubernetes-anywhere with a single kubeadm-powered stage?

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 20, 2017
@luxas
Copy link
Member

luxas commented Dec 22, 2017

/remove-lifecycle stale

SIG Cluster Lifecycle is looking into reprioritizing this in 2018

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 22, 2017
@luxas
Copy link
Member

luxas commented Dec 22, 2017

cc @kubernetes/sig-cluster-lifecycle-feature-requests

@k8s-ci-robot k8s-ci-robot added sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. kind/feature Categorizes issue or PR as related to a new feature. labels Dec 22, 2017
@chrislovecnm
Copy link
Contributor

You added the stale label btw

@luxas
Copy link
Member

luxas commented Dec 25, 2017

@chrislovecnm Sorry, I don't understand your comment?

@errordeveloper
Copy link
Member Author

I've just cross posted on the mailing lists about this: https://groups.google.com/d/msg/kubernetes-sig-docs/GFnX8DRw7iY/8y3feBK5AAAJ.

cc @roberthbailey

@roberthbailey
Copy link
Contributor

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.

@errordeveloper
Copy link
Member Author

Now tracked in #7278.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 14, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 13, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Projects
None yet
Development

No branches or pull requests

10 participants