Enhancements: Extensible configuration/invocation of `kubeadm`

[luxas]

Feature Description

• One-line feature description (can be used as a release note): kubeadm will have a new kubeadm phase command that supports performing only subtasks of the full kubeadm init flow. Combined with fine-grained configuration kubeadm will be easily consumable by higher-level tools like kops or GKE.
• Primary contact (assignee): @luxas @justinsb
• Responsible SIGs: @kubernetes/sig-cluster-lifecycle-feature-requests
• Design proposal link (community repo): https://github.com/kubernetes/kubeadm/blob/master/docs/design/design_v1.8.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: @timothysc @mikedanese
• Approver (likely from SIG/area to which feature belongs): @jbeda @mikedanese
• Feature target (which target equals to which milestone):
  
  
  
  • Alpha release target (x.y): v1.6
  
  
  • Beta release target (x.y): v1.12
  
  
  • Stable release target (x.y): TBD
  
  

[luxas]

This will stay in alpha for one more release, but has seen significant improvement since v1.7
It is next to beta-level quality, but we still want to collect a little bit more feedback before graduating it.

[idvoretskyi]

@luxas @justinsb @kubernetes/sig-cluster-lifecycle-feature-requests can you confirm that this feature targets 1.8?

If yes, please, update the features tracking spreadsheet with the feature data, otherwise, let's remove this item from 1.8 milestone.

Thanks

[luxas]

@idvoretskyi This is targeting v1.8 indeed.
Added this to the feature spreadsheet as well

[luxas]

This will probably stay in alpha in v1.9 as it depends somewhat on the Cluster API work and different ComponentConfig implements from other SIGs

[zacharysarah]

@luxas :wave: 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]

Docs PR: https://github.com/kubernetes/website/pull/6103

[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

[fejta-bot]

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

[justaugustus]

@luxas
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 incremental progress will be made, but not targeting beta yet.

/lifecycle frozen

[kacole2]

@luxas This feature was worked on in the previous milestone, so we'd like to check in and see if there are any plans for this to graduate stages in Kubernetes 1.12 as mentioned in your original post. This still has the 1.11 milestone as well so we need to update it accordingly.

If there are any updates, please explicitly ping @justaugustus, @kacole2, @robertsandoval, @rajendar38 to note that it is ready to be included in the Features Tracking Spreadsheet for Kubernetes 1.12.

---

Please note that the Features Freeze is July 31st, after which any incomplete Feature issues will require an Exception request to be accepted into the milestone.

In addition, please be aware of the following relevant deadlines:

• Docs deadline (open placeholder PRs): 8/21
• Test case freeze: 8/28

Please make sure all PRs for features have relevant release notes included as well.

Happy shipping!

[luxas]

We're hoping to graduate this to beta in v1.12

[kacole2]

@justaugustus can you add the tracked label here, please?

[justaugustus]

Done. Thanks for the updates, @luxas!

[justaugustus]

/kind feature

[zparnold]

Hey there! @luxas I'm the wrangler for the Docs this release. Is there any chance I could have you open up a docs PR against the release-1.12 branch as a placeholder? That gives us more confidence in the feature shipping in this release and gives me something to work with when we start doing reviews/edits. Thanks! If this feature does not require docs, could you please update the features tracking spreadsheet to reflect it?

[justaugustus]

@luxas @justinsb @timothysc --
Any update on docs status for this feature? Are we still planning to land it for 1.12?
At this point, code freeze is upon us, and docs are due on 9/7 (2 days).
If we don't here anything back regarding this feature ASAP, we'll need to remove it from the milestone.

cc: @zparnold @jimangel @tfogo

[neolit123]

so the kubeadm commands that this feature covers, remain under kubeadm alpha phase, because we didn't have the time to move them, but they are in a beta state.

in terms of documentation the commands are are already well covered in multiple k/website pages:
https://kubernetes.io/docs/reference/setup-tools/kubeadm/implementation-details/
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-alpha/
https://kubernetes.io/docs/setup/independent/setup-ha-etcd-with-kubeadm/

i'm on the fence here given the remaining alpha tag, but i'm leaning towards :+1: for beta on this one for 1.12.

[tpepper]

Would there be a commit to remove alpha in that command then?

[neolit123]

@tpepper it's too late for 1.12 as such a PR would have the kind/feature
we have this planned for 1.13:
https://github.com/kubernetes/kubeadm/issues/454

[justaugustus]

Thanks for the update, @neolit123!

[timothysc]

Our intention is to take kubeadm to GA in 1.13 which would include this item.

[spiffxp]

/stage stable
@kacole2 this should be bumped to stable in the spreadsheet

[npentrel]

Hi @luxas, I'm Naomi working on docs for the 1.13 release. Can you please open a placeholder PR against dev-1.13 for this issue?

[timothysc]

Closing in favor of #11 .

We are in the final stages now of moving towards GA.