Move kubeadm out of kubernetes/kubernetes

[neolit123]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  Move kubeadm out of kubernetes/kubernetes in the kubernetes/kubeadm repository
• Kubernetes Enhancement Proposal: (link to kubernetes/enhancements file, if none yet, link to PR)
  KEP is WIP: kubeadm: add KEP for moving kubeadm out of k/k #1425
• Primary contact (assignee): @neolit123
• Responsible SIGs: Cluster Lifecycle
• Enhancement target (which target equals to which milestone):
  (NOT applicable, ideally the move should happen in one release)
  • Alpha release target (x.y)
  • Beta release target (x.y)
  • Stable release target: TODO

Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement

This issue is only created to comply with the the KEP template item:

kubernetes/enhancements issue in release milestone, which links to KEP (this should be a link to the KEP location

tracking issue in k/kubeadm:
kubernetes/kubeadm#1949

[jeremyrickard]

Hey there @neolit123 -- 1.18 Enhancements lead here. I wanted to check in and see if you think this Enhancement will be graduating to stable in 1.18? It looks like you're targeting that.

The current release schedule is:

Monday, January 6th - Release Cycle Begins
Tuesday, January 28th EOD PST - Enhancements Freeze
Thursday, March 5th, EOD PST - Code Freeze
Monday, March 16th - Docs must be completed and reviewed
Tuesday, March 24th - Kubernetes 1.18.0 Released

As a reminder, the KEP will need to be merged in the implementable state to be included in the milestone.

If you do, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

[neolit123]

thanks for the heads up @jeremyrickard

As a reminder, the KEP will need to be merged in the implementable state to be included in the milestone.

the KEP is still under review and it's not clear whether it will be merged as implementable before the 28th.

will keep you updated.
thanks.

[jeremyrickard]

@neolit123 i've been tracking and it looks like the KEP might be good to merge in time for the Enhancements Freeze? I'll track this and if we hit the enhancement freeze and it's not merged, we can circle back and update things and move it out of the milestone. Sound good?

[neolit123]

SGTM

[neolit123]

@jeremyrickard

as noted on the #sig-release slack channel this work might span multiple releases. i think it's appropriate to mark this ticket as v1.19.

not sure if "tracked/yes" should still be present at this point.