search

kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.33k stars 1.44k forks source link

Introduce compatibility version for Kubernetes control-plane upgrades #4330

Open logicalhan opened 8 months ago

logicalhan commented 8 months ago

Enhancement Description

Introduce compatibility version in Kubernetes components to enhance Kubernetes control-plane upgrades. See safer Kubernetes upgrades for more details.

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

jeremyrickard commented 8 months ago

/sig api-machinery

jpbetz commented 5 months ago

/sig architecture

jpbetz commented 5 months ago

/milestone 1.30

k8s-ci-robot commented 5 months ago

@jpbetz: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.

In response to [this](https://github.com/kubernetes/enhancements/issues/4330#issuecomment-1905099603): >/milestone 1.30 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.
jpbetz commented 5 months ago

/milestone v1.30

johnbelamaric commented 5 months ago

/lead-opted-in

jpbetz commented 5 months ago

/label lead-opted-in

mickeyboxell commented 4 months ago

Hello @logicalhan 👋, Enhancements team here.

Just checking in as we approach enhancements freeze today ([02:00 UTC Friday 9th February 2024 / 18:00 PDT Thursday 8th February 2024](https://everytimezone.com/s/1ade3dca)):.

This enhancement is targeting for stage alpha for v1.30 (correct me, if otherwise)

Here's where this enhancement currently stands:

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

mickeyboxell commented 4 months ago

Hello 👋, v1.30 Enhancements team here.

Unfortunately, this enhancement did not meet requirements for enhancements freeze.

If you still wish to progress this enhancement in {current release}, please file an exception request. Thanks!

salehsedghpour commented 4 months ago

/milestone clear

jpbetz commented 4 months ago

This is due to a clerical error. https://github.com/kubernetes/enhancements/pull/4395 was intended to be the KEP PR but we neglected to notice is was still marked as provisional. https://github.com/kubernetes/enhancements/pull/4502 fixes this.

salehsedghpour commented 4 months ago

@jpbetz Please make sure that #4502 is being merged and also consider filing an exception request.

jpbetz commented 4 months ago

@jpbetz Please make sure that #4502 is being merged and also consider filing an exception request.

https://github.com/kubernetes/enhancements/pull/4502 is merged. Do we need a full exception for a clerical error like this?

salehsedghpour commented 4 months ago

With #4502 being merged, this Enhancements is now tracked for the enhancements freeze. No need to file an exception.

kcmartin commented 4 months ago

Hi @jpbetz,

👋 from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement!

We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating.

To opt in, you need to open a Feature Blog placeholder PR against the website repository. The placeholder PR deadline is 27th February, 2024. Here's the 1.30 Release Calendar

drewhagen commented 4 months ago

Hello @jpbetz 👋, 1.30 Docs Lead here.

Does this enhancement work planned for 1.30 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday February 22nd 2024 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you!

mickeyboxell commented 4 months ago

Hey again @jpbetz 👋 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 .

Here's where this enhancement currently stands:

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP.

As always, we are here to help if any questions come up. Thanks!

mickeyboxell commented 4 months ago

Hey @jpbetz 👋 Enhancements team here, just a friendly reminder to follow up on the open Enhancement items above prior to code freeze at 02:00 UTC Wednesday 6th March 2024.

jpbetz commented 4 months ago

@siyuanfoundation @liggitt @deads2k and I discussed this enhancement. We've got a core implementation that's looking good, but it needs to integrate seamlessly in with feature gates, and in particular feature gates in composed sub-components (e.g. a feature gated client-go composed inside some other component that has it's own feature gates).

We've decided to defer merging the implementation until the start of the 1.31 merge window. This both de-risks the 1.30 release and gives us time to more fully get this ready.

/milestone v1.31

sreeram-venkitesh commented 1 month ago

Hello @jpbetz @logicalhan 👋, v1.31 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.

This enhancement is targeting for stage alpha for v1.31 (correct me, if otherwise)

Here's where this enhancement currently stands:

For this KEP, since it was already tracked for enhancements freeze in v1.30 but was deferred for v1.31, we're almost good to go. We only need to make a few changes to the kep.yaml file.

The status of this enhancement is marked as at risk for enhancement freeze. But I can mark it as tracked as soon as the above changes are merged. Please make sure to get this done before the enhancements freeze.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Let me know if you have any questions! Thank you!

chanieljdan commented 3 weeks ago

Hi @jpbetz @logicalhan 👋, 1.31 Docs Shadow here.

Does this enhancement work planned for 1.31 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday June 27, 2024 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarized with the docs requirement for the release.

Thank you!

Daniel

siyuanfoundation commented 3 weeks ago

sreeram-venkitesh

Thank you @sreeram-venkitesh, I have opened https://github.com/kubernetes/enhancements/pull/4716, PTAL

sreeram-venkitesh commented 3 weeks ago

@siyuanfoundation Thanks for pinging, I will mark this KEP as Tracked for enhancements freeze with #4716 merged! 🎉

siyuanfoundation commented 2 weeks ago

Hi @jpbetz @logicalhan 👋, 1.31 Docs Shadow here.

Does this enhancement work planned for 1.31 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday June 27, 2024 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarized with the docs requirement for the release.

Thank you!

Daniel

@chanieljdan draft doc PR opened in https://github.com/kubernetes/website/pull/46872

hailkomputer commented 2 weeks ago

Hi @logicalhan, @jpbetz, @liggitt

:wave: from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines.

Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

Princesso commented 1 week ago

@siyuanfoundation thanks for sharing a link to the Doc draft PR. I noticed that the PR is closed. Is there any plan to reopen it anytime soon before the June 27 deadline?

siyuanfoundation commented 1 week ago

@Princesso Thanks for the reminder. We don't need any doc change except the auto generated command line flag change. Would that be ok?

siyuanfoundation commented 1 week ago

opened doc placeholder https://github.com/kubernetes/website/pull/47007, @chanieljdan opened blog placeholder https://github.com/kubernetes/website/pull/47006, @hailkomputer