search

kubernetes / enhancements

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

Deprecate status.nodeInfo.kubeProxyVersion field #4004

Open HirazawaUi opened 1 year ago

HirazawaUi commented 1 year ago

Enhancement Description

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

HirazawaUi commented 1 year ago

/sig node /cc @danwinship /assign

HirazawaUi commented 1 year ago

/cc @thockin

SergeyKanzhelev commented 1 year ago

/milestone v1.28

thockin commented 1 year ago

What the staus on this? Alpha in 29?

HirazawaUi commented 1 year ago

What the staus on this? Alpha in 29?

Yes, we'll be in Alpha at v1.29

SergeyKanzhelev commented 1 year ago

/milestone v1.29 /label lead-opted-in

npolshakova commented 1 year ago

Hello @HirazawaUi 👋, 1.29 Enhancements team here!

Just checking in as we approach enhancements freeze on 01:00 UTC, Friday, 6th October, 2023.

This enhancement is targeting for stage alpha for 1.29 (correct me, if otherwise)

Here's where this enhancement currently stands:

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

krol3 commented 1 year ago

Hi @HirazawaUi 👋, v1.29 Communication Release Team. I would like to check any plan about publication blogs related new features, removals, and deprecations for this release.

You need to open a PR placeholder in the website repository. The deadline will be on Thursday 19th October 2023 Here the 1.29 Calendar

HirazawaUi commented 1 year ago

Ok, I've opened a PR placeholder in the website repository, thanks for the tip!

harshitasao commented 12 months ago

Hi @HirazawaUi 👋, v1.29 Docs Shadow here Does this enhancement work planned for v1.29 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.29 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, 19 October 2023. Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you!

HirazawaUi commented 12 months ago

I have opened a placeholder PR at k/website.

AnaMMedina21 commented 11 months ago

Hello @sanposhiho 👋, v1.29 Enhancements team here.

Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November 2023

Here's where this enhancement currently stands:

Missing Approval on https://github.com/kubernetes/website/pull/43348 and https://github.com/kubernetes/kubernetes/pull/120954

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

With all this, the status of this KEP is At Risk for Code Freeze.

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

npolshakova commented 11 months ago

Hello @sanposhiho👋, 1.29 Enhancements team here.

With all the implementation(code related) PRs merged as per the issue description, this enhancement is now marked as tracked for code freeze for the 1.29 Code Freeze! 🚀

The test freeze is 01:00 UTC Wednesday 15th November 2023 / 18:00 PDT Tuesday 14th November 2023. Please make sure all test PRs are merged in by then. Let me know if there are additional test PRs we should track. Thanks!

kcmartin commented 10 months ago

@HirazawaUi @sanposhiho Hi, 1.29 Comms Team again! You indicated you were planning to write a blog post for this feature. A reminder that today (November 14, 2023) is the deadline for opening a Draft blog PR. We noticed Docs PRs, but no blog PR. Would you please update us about your plans?

HirazawaUi commented 10 months ago

This is just a simple mini-KEP, I think there is no need for blog PR.

salehsedghpour commented 9 months ago

/remove-label lead-opted-in

salehsedghpour commented 8 months ago

Hello 👋 1.30 Enhancements Lead here,

I'm closing milestone 1.29 now, If you wish to progress this enhancement in v1.30, please follow the instructions here to opt in the enhancement and make sure the lead-opted-in label is set so it can get added to the tracking board and finally add /milestone v1.30. Thanks!

/milestone clear

HirazawaUi commented 8 months ago

At 1.30, it won't make any changes.

thockin commented 5 months ago

@HirazawaUi Will you move this to beta for 1.31?

HirazawaUi commented 5 months ago

@HirazawaUi Will you move this to beta for 1.31?

Yes, in the process of implementation https://github.com/kubernetes/kubernetes/pull/123845

SergeyKanzhelev commented 4 months ago

/label lead-opted-in /stage stable

SergeyKanzhelev commented 4 months ago

/stage beta

sreeram-venkitesh commented 4 months ago

Hello @HirazawaUi 👋, 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 beta for v1.31 (correct me, if otherwise)

Here's where this enhancement currently stands:

For this KEP, everything is taken care of in https://github.com/kubernetes/enhancements/pull/4625. Please make sure that it is merged in time before the enhancements freeze.

The status of this enhancement is marked as at risk for enhancement freeze. I can mark it as tracked as soon as the above PR is merged however! Please link the relevant PRs for beta in the issue description as well.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

sreeram-venkitesh commented 3 months ago

With #4625 merged, we can mark this KEP as tracked for enhancements freeze! 🎉

mbianchidev commented 3 months ago

Hello again @HirazawaUi @danwinship (hope you both read this one after the other comments so that "again" makes sense 😄 )

: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. Or like in this case a deprecation & removal.

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.

mbianchidev commented 3 months ago

Hello again @HirazawaUi @danwinship (hope you both read this one after the other comments so that "again" makes sense 😄 )

👋 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. Or like in this case a deprecation & removal.

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.

Reminder of the 3rd of July deadline! It's totally fine to also opt out if you don't think that writing a blog is useful for our users or if you don't have time (in that case team comms can also help you out :eyes: )

HirazawaUi commented 3 months ago

@mbianchidev Thanks for the heads up, but I see @a-mccarthy has already added a PR for the blog, I'll ask if my assistance is needed to complete it

a-mccarthy commented 3 months ago

@HirazawaUi just to clarify, we are planning to include this in the Deprecations and Removal blog for 1.31. However, if you feel that this change requires a separate, full blog article to help users understand the changes, please open placeholder PR. perfectly ok, if the full blog post is not needed. thanks! :)

sreeram-venkitesh commented 3 months ago

Hey again @HirazawaUi 👋 v1.31 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.

Here's where this enhancement currently stands:

List of associated PRs:

If you anticipate missing code freeze, you can file an exception request in advance.

This KEP is marked as Tracked for code freeze. Thanks a lot for keeping the issue description up to date! 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!

liggitt commented 1 month ago

I missed that this was wanting to promote to beta in 1.31 ... because this is clearing population of a stable API field, the minimum period from announcement (in 1.29) is 1 year, so 1.33 is the earliest this can default to clearing. I'll open a revert of the enablement for master / 1.31

kannon92 commented 1 month ago

I'm not sure with @liggitt point if this KEP will be worked on 1.32. Please let me know if you want reviews for the KEP from sig-node in 1.32.

liggitt commented 1 month ago

I think it would stay as-is for 1.32 and default-enable in 1.33

tjons commented 2 weeks ago

Hi, enhancements lead here - I inadvertently added this to the 1.32 tracking board 😀. Please readd it if you wish to progress this enhancement in 1.32.

/remove-label lead-opted-in