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.

[jeremyrickard]

/milestone v1.19

[fejta-bot]

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

[neolit123]

we are going to push to clear the picture around this effort, but 1.19 is unlikely at this point.

/milestone clear
/remove-lifecycle stale

[palnabarun]

Hi @neolit123 -- Thank you for the updates on this. 🙂

[fejta-bot]

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

[neolit123]

/remove-lifecycle stale

[kikisdeliveryservice]

Hi @neolit123

Enhancements Lead here. Any plans for this in 1.20?

Thanks!
Kirsten

[neolit123]

Hi. Likely no work for this will happen in .20. Our efforts are delayed on some decision making.

[kikisdeliveryservice]

Thank you for the fast update! Let us know if anything changes.

Best,
Kirsten

[fejta-bot]

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

[neolit123]

/remove-lifecycle stale

[neolit123]

update: kubectl is ahead of kubeadm in terms of plans for moving out. kubeadm will most likely follow the established path by kubectl and participate in discussions with sig-release/arch.

[lasomethingsomething]

Documenting here the ask from SIG Release: provide outline offering specific guidance on how to build and ship artefacts of things when the source code is not within kubernetes/kubernetes (for things that are getting split out of kubernetes/kubernetes).

Some relevant info from SIG CL in this deck.

[palnabarun]

/assign

I am investigating things that we need to achieve the above for kubectl.

[jeremyrickard]

We'll update this to reflect that kubectl will be worked to move in 1.23, kubeadm will not be the focus for 1.23

[neolit123]

@jeremyrickard could you please ping the SIG Cluster Lifecycle ML / slack when the discussions with SIG CLI begin about the kubectl extraction?

[palnabarun]

@neolit123 -- Surely! :)

[jeremyrickard]

@palnabarun any updates that you can share for this?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale