search

kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.41k stars 1.47k forks source link

New kubeadm component config scheme #1381

Open rosti opened 4 years ago

rosti commented 4 years ago

Enhancement Description

kubeadm tracking issue: https://github.com/kubernetes/kubeadm/issues/1681

rosti commented 4 years ago

/sig cluster-lifecycle

rosti commented 4 years ago

/assign

palnabarun commented 4 years ago

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:

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 commented 4 years ago

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

palnabarun commented 4 years ago

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

rosti commented 4 years ago

@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 commented 4 years ago

@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 commented 4 years ago

/milestone 1.19

k8s-ci-robot commented 4 years ago

@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](https://github.com/kubernetes/enhancements/issues/1381#issuecomment-578682972): >/milestone 1.19 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
palnabarun commented 4 years ago

/stage alpha /milestone v1.19

fejta-bot commented 4 years ago

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 commented 4 years ago

/remove-lifecycle stale

palnabarun commented 4 years ago

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

rosti commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

Hi @rosti,

Tomorrow, Tuesday May 19 EOD Pacific Time is Enhancements Freeze

Will this enhancement be part of the 1.19 release cycle?

neolit123 commented 4 years ago

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

palnabarun commented 4 years ago

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

mikejoh commented 4 years ago

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 commented 4 years ago

@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:

palnabarun commented 4 years ago

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 commented 4 years ago

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

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

rosti commented 4 years ago

In flight PRs for 1.19

Implementation:

Docs:

CC @palnabarun @mikejoh

palnabarun commented 4 years ago

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:

palnabarun commented 4 years ago

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 commented 4 years ago

@palnabarun all code PRs merged.

palnabarun commented 4 years ago

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

kikisdeliveryservice commented 4 years ago

/milestone clear

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

kikisdeliveryservice commented 4 years ago

Hi @rosti @neolit123

Enhancements Lead here. Any plans for this in 1.20?

Thanks! Kirsten

neolit123 commented 4 years ago

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

kikisdeliveryservice commented 4 years ago

Hi @neolit123

Any updates? Just double checking on 1.20 plans.

Thanks, Kirsten

neolit123 commented 4 years ago

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

fejta-bot commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

/remove-lifecycle stale

k8s-triage-robot commented 3 years ago

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:

You can:

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

/lifecycle stale

k8s-triage-robot commented 3 years ago

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

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

You can:

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

/lifecycle rotten

neolit123 commented 3 years ago

/remove-lifecycle rotten

k8s-triage-robot commented 2 years ago

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:

You can:

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

/lifecycle stale