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

Jump to bottom

kubeadm phases to beta #2501

Closed
4 tasks
shekhar-rajak opened this issue Feb 12, 2021 · 3 comments
Closed
4 tasks

kubeadm phases to beta #2501

shekhar-rajak opened this issue Feb 12, 2021 · 3 comments
Labels
needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one.

Comments

@shekhar-rajak
Copy link
Contributor

Enhancement Description

  • One-line enhancement description (can be used as a release note): kubeadm phases to beta
  • Kubernetes Enhancement Proposal:
We are defining the road map for graduating `kubeadm alpha phase` commands to
beta, addressing concerns/lessons learned so far about the additional
effort for maintenance of this feature.
  • Discussion Link:
  • Primary contact (assignee): @fabriziopandini
  • Responsible SIGs: sig-cluster-lifecycle
  • Enhancement target (which target equals to which milestone):
    • Alpha release target (x.y):
    • Beta release target (x.y):
    • Stable release target (x.y):
  • Alpha
    • KEP (k/enhancements) update PR(s):
    • Code (k/k) update PR(s):
    • Docs (k/website) update PR(s):

Implementation History

  • #61631 First prototype implementation
    (now outdated)
  • v1.13 implementation of phases in the kubeadm init workflow
  • v1.14 implementation of phases in the kubeadm join workflow
  • v1.15 implementation of phases in the kubeadm upgrade node workflow
  • v1.17 implementation of phases in the kubeadm upgrade apply workflow (planned)

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
@k8s-ci-robot
Copy link
Contributor

@shekhar-rajak: There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

  • /sig <group-name>
  • /wg <group-name>
  • /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Feb 12, 2021
@shekhar-rajak
Copy link
Contributor Author

Migrating all the old template keps to new template : #2499

@neolit123
Copy link
Member

this feature is GA at this point so we can close this ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@neolit123 @k8s-ci-robot @shekhar-rajak