Integrate Cluster Bootstrap/Discovery with Kubenetes Core

[jbeda]

Feature Description

• One-line feature description (can be used as a release note): Add a new authentication and verification mechanism called Bootstrap Tokens to use to easily add new members to a cluster
• Primary contact (assignee): @luxas @jbeda
• Responsible SIGs: sig/cluster-lifecycle, sig/auth
• Design proposal link (community repo): Update the token discovery proposal community#628
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @mikedanese @liggitt @ericchiang
• Approver (likely from SIG/area to which feature belongs): @mikedanese @liggitt @ericchiang
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y): v1.6
  • Beta release target (x.y): v1.8
  • Stable release target (x.y): TODO

[idvoretskyi]

@jbeda I noticed that the feature has been opened after the agreed submission deadline (Oct 10). Is there any reason why this feature has to be added to 1.5 milestone?

[jbeda]

@idvoretskyi I screwed up and I apologize. We were tracking all of the work in the the lifecycle SIG and met on Tuesday morning. Missed it by one day. Hopefully this isn't a blocker?

[mikedanese]

meta: I don't understand the 1.5 milestone deadline. If a feature get's dreamed up after the deadline, alpha implemented and merged before we cut 1.5 is it still a feature? I see the purpose of this repo as providing visibility to progress on large features. I don't see any purpose to a submission deadline. There's also no documentation of a deadline in this repo (when or why).

[idvoretskyi]

@mikedanese the purpose of the repo - is providing visibility and tracking on the product features, you are right. At the same time, during the release development process, we'd like to see the actual picture of the features that are going to be added to the product.
Feature submission deadline - is not the deadline for developing the feature; it's a deadline for declaring your desire to develop some functionality that you'd like to see in the released product. We are expecting from all the contributors to follow the release roadmap carefully to avoid unnecessary planning chaos.
PS. Thank you for mentioning the reflecting the deadline in the documentation - I've submitted a PR to add it to the release roadmap #133.

[idvoretskyi]

@jbeda as we have already agreed in the mailing thread [0], this is not a blocker.
0. https://groups.google.com/d/msg/kubernetes-sig-cluster-lifecycle/AyNEsX2lJnU/Hv0SYJFJEgAJ

[jbeda]

cc @kubernetes/sig-cluster-lifecycle