Ability to create dynamic HA clusters with kubeadm

[luxas]

Feature Description

• One-line feature description (can be used as a release note): Dynamic HA clusters can easily be created with the kubeadm tool using exactly the same kubeadm init and kubeadm join commands the users are familiar with.
• Primary contact (assignee): @luxas @timothysc
• Responsible SIGs: @kubernetes/sig-cluster-lifecycle-feature-requests
• Design proposal link (community repo): https://docs.google.com/document/d/1P3oUJ_kdaRSTlGONujadGBpYegjn4RjBNZLHZ4zU7lI/edit#
• Related KEPS:
  https://github.com/kubernetes/enhancements/blob/master/keps/sig-cluster-lifecycle/kubeadm/0015-kubeadm-join-control-plane.md
  https://github.com/kubernetes/enhancements/blob/master/keps/sig-cluster-lifecycle/kubeadm/20190122-Certificates-copy-for-kubeadm-join--control-plane.md
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @fabriziopandini @timothysc
• Approver (likely from SIG/area to which feature belongs): @fabriziopandini @timothysc
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y): v1.9
  • Beta release target (x.y): v1.15
  • Stable release target (x.y): v1.24

---

Edit by @spiffxp:

Per #357 (comment) we should consider kicking this out of of v1.14 and using a separate tracking issue for the actual KEP being implemented this cycle: 20190122-Certificates-copy-for-kubeadm-join--control-plane.md

[luxas]

Hoping to get an alpha implementation of this in v1.8. Might or might not work out. At least a ready design doc should be ready at the end of the v1.8 cycle.

[luxas]

@kubernetes/sig-cluster-lifecycle-feature-requests I moved this to next-milestone as no code for this is shipping in v1.8, only design

[luxas]

Targeting alpha in v1.9

[zacharysarah]

@luxas 👋 Please indicate in the 1.9 feature tracking board
whether this feature needs documentation. If yes, please open a PR and add a link to the tracking spreadsheet. Thanks in advance!

[luxas]

This feature didn't make it into v1.9

[idvoretskyi]

@luxas @kubernetes/sig-cluster-lifecycle-feature-requests still on track for 1.10?

[roberthbailey]

This has been de-prioritized for 1.10 in favor of trying to get the existing kubeadm functionality promoted from beta to GA.

[idvoretskyi]

@roberthbailey thanks

[justaugustus]

@luxas / @timothysc -- Any plans for this in 1.11?

If so, can you please ensure the feature is up-to-date with the appropriate:

• Description
• Milestone
• Assignee(s)
• Labels:
  • stage/{alpha,beta,stable}
  • sig/*
  • kind/feature

cc @idvoretskyi

[luxas]

@justaugustus No plans to move feature state this release, incremental improvements.

/lifecycle frozen

[justaugustus]

/remove-lifecycle frozen

[neolit123]

/remove-lifecycle stale

[kikisdeliveryservice]

Hi @neolit123

Enhancements Lead here. Any plans for this to graduate in 1.20?

Thanks,
Kirsten

[k8s-mirror-cluster-lifecycle-feature-re]

Hi, we haven't decided yet, but more likely not for 1.20. kubernetes/kubeadm#2081

[kikisdeliveryservice]

Thanks, I will keep this as untracked, please let us know if anything changes so we can properly tracks & milestone this KEP.

[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

[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-contributor-experience at kubernetes/community.
/lifecycle stale

[neolit123]

/remove-lifecycle stale

[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-contributor-experience at kubernetes/community.
/lifecycle stale

[k8s-mirror-cluster-lifecycle-feature-re]

/remove-lifecycle stale

[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

[neolit123]

/remove-lifecycle stale

[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