Enhancements: New kubeadm component config scheme

[rosti]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  New kubeadm component config scheme
• Kubernetes Enhancement Proposal:
  https://github.com/kubernetes/enhancements/blob/master/keps/sig-cluster-lifecycle/kubeadm/20190925-component-configs.md
• Primary contact (assignee): @rosti
• Responsible SIGs: sig-cluster-lifecycle
• Enhancement target (which target equals to which milestone):
  
  
  
  • Alpha release target (x.y) TBD
  
  
  • Beta release target (x.y) TBD
  
  
  • Stable release target (x.y) TBD
  
  

[rosti]

/sig cluster-lifecycle

[rosti]

/assign

[palnabarun]

Hey there @rosti -- 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to __alpha__ in 1.18 or having a major change in it's current level?

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

To be included in the release,

1. The KEP PR must be merged
2. The KEP must be in an implementable state
3. The KEP must have test plans and graduation criteria.

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

We'll be tracking enhancements here: http://bit.ly/k8s-1-18-enhancements

Thanks! :)

[palnabarun]

@rosti Just a friendly reminder, we are just 7 days away from the Enhancement Freeze (Tuesday, January 28th).

[palnabarun]

@rosti Just a friendly reminder, we are just 2 days away from the Enhancement Freeze (3 PM Pacific Time, Tuesday, January 28th).

[rosti]

@palnabarun sorry for the late response. Although most of this is going to be merged in 1.18, it probably won't be graduating to alpha in this release.

[palnabarun]

@rosti Thank you for the updates. I will defer this to the 1.19 cycle. We can track it in the next release cycle.

[palnabarun]

/milestone 1.19

[k8s-ci-robot]

@palnabarun: The provided milestone is not valid for this repository. Milestones in this repository: [keps-beta, keps-ga, v1.17, v1.18, v1.19, v1.20, v1.21]

Use /milestone clear to clear the milestone.

In response to this:

/milestone 1.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[palnabarun]

/stage alpha
/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]

/remove-lifecycle stale

[palnabarun]

Hi @rosti -- 1.19 Enhancements Lead here, just wanted to confirm if this enhancement will graduate to Alpha in 1.19?

[rosti]

Hi @palnabarun I am in the process of preparing a KEP update. I guess that if that merges before enhancements freeze, this might be achievable.

[palnabarun]

Thank you @rosti for the update.

Just FYI, in order to have this part of the release:

1. The KEP PR must be merged in an implementable state
2. The KEP must have test plans
3. The KEP must have graduation criteria.

I will check back later for the status. :+1:

[palnabarun]

Hi @rosti, pinging back to check if a PR to update the KEP is in flight. If so, can you please link it here so that we can track it? Let me otherwise too. :slightly_smiling_face:

[palnabarun]

Hi @rosti,

Tomorrow, Tuesday May 19 EOD Pacific Time is Enhancements Freeze

Will this enhancement be part of the 1.19 release cycle?

[neolit123]

@palnabarun hi, yes the KEP update merged here:
https://github.com/kubernetes/enhancements/pull/1725

[palnabarun]

@neolit123 -- Ack. Thanks for the update. I have updated the tracking sheet. :+1:

[mikejoh]

Hello, @rosti ! :wave: I'm one of the v1.19 Docs shadows. Does this enhancement work planned for v1.19 require any new docs (or modifications to existing docs)?

This is a friendly reminder that we're looking for a PR against kubernetes/website (branch dev-1.19) due by Friday, June 12, it can just be a placeholder PR at this time. Let me know if you have any questions!

Regards,
Mikael.

[palnabarun]

@rosti @neolit123 -- Can you please link to all the implementation PR's here - k/k or otherwise? :slightly_smiling_face:

---

The current release schedule is:

• ~Monday, April 13: Week 1 - Release cycle begins~
• ~Tuesday, May 19: Week 6 - Enhancements Freeze~
• Thursday, June 25: Week 11 - Code Freeze
• Thursday, July 9: Week 14 - Docs must be completed and reviewed
• Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released

[palnabarun]

Can you please link to all the implementation PR's here - k/k or otherwise?

@rosti @neolit123 -- Pinging back as a reminder of the above. :slightly_smiling_face:

[neolit123]

LGTM / approved
https://github.com/kubernetes/kubernetes/pull/86070

@rosti i'd defer to you to enumerate other PRs if needed.

[rosti]

In flight PRs for 1.19

Implementation:

• kubernetes/kubernetes#86070 (merged)
• kubernetes/kubernetes#91980
• kubernetes/kubernetes#88124

Docs:

• kubernetes/website#21663

CC @palnabarun @mikejoh

[palnabarun]

Hi @rosti -- Thank you for linking all the implementation PRs here. I have updated the tracking sheet with the same. :+1:

The release timeline has been revised recently, more details of which can be found here.

Please let me know if you have any questions. :slightly_smiling_face:

---

The revised release schedule is:

• Thursday, July 9th: Week 13 - Code Freeze
• Thursday, July 16th: Week 14 - Docs must be completed and reviewed
• Tuesday, August 25th: Week 20 - Kubernetes v1.19.0 released

[palnabarun]

Hi @rosti :wave:, I saw that all the linked PRs above are merged. Do you have any more code PRs or is the feature code complete?

Thank you. :slightly_smiling_face:

[neolit123]

@palnabarun all code PRs merged.

[palnabarun]

@neolit123 -- Thank you for the update. :+1:

[kikisdeliveryservice]

/milestone clear

(removing this enhancement issue from the v1.19 milestone as the milestone is complete)

[kikisdeliveryservice]

Hi @rosti @neolit123

Enhancements Lead here. Any plans for this in 1.20?

Thanks!
Kirsten

[neolit123]

Hi. We don't have plans to add a new API version in .20. But this is still
to be decided this week.

[kikisdeliveryservice]

Hi @neolit123

Any updates? Just double checking on 1.20 plans.

Thanks,
Kirsten

[neolit123]

hi, sorry for the delayed reply. we decided to not track this issue for 1.20.