Deprecate status.nodeInfo.kubeProxyVersion field

[HirazawaUi]

Enhancement Description

• One-line enhancement description (can be used as a release note): Deprecate the status.nodeInfo.kubeProxyVersion field of v1.Node
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/4004-deprecate-kube-proxy-version
• Discussion Link: https://github.com/kubernetes/kubernetes/issues/117756
• Primary contact (assignee): @HirazawaUi
• Responsible SIGs: sig-node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): v1.29
  • Beta release target (x.y): v1.31
  • Stable release target (x.y): v1.33
• [x] Alpha
  • [x] KEP (k/enhancements) update PR(s):
    • [x] #4005
    • [x] #4199
  • [x] Code (k/k) update PR(s):
    • [x] https://github.com/kubernetes/kubernetes/pull/120954
    • [x] https://github.com/kubernetes/kubernetes/pull/123845
  • [x] Docs (k/website) update PR(s):
    • [x] https://github.com/kubernetes/website/pull/43348
• [ ] Beta
  • [x] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/4625
  • [x] Code (k/k) update PR(s): https://github.com/kubernetes/kubernetes/pull/123845
  • [x] Docs (k/website) update(s): https://github.com/kubernetes/website/pull/46935

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

[HirazawaUi]

/sig node /cc @danwinship /assign

[HirazawaUi]

/cc @thockin

[SergeyKanzhelev]

/milestone v1.28

[thockin]

What the staus on this? Alpha in 29?

[HirazawaUi]

What the staus on this? Alpha in 29?

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

[SergeyKanzhelev]

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

[npolshakova]

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:

• [x] KEP readme using the latest template has been merged into the k/enhancements repo.
• [x] KEP status is marked as implementable for latest-milestone: 1.29. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• [x] KEP readme has up-to-date graduation criteria
• [x] KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

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]

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]

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

[harshitasao]

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]

I have opened a placeholder PR at k/website.

[AnaMMedina21]

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:

• [ ] All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• [ ] All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

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]

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]

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

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

[salehsedghpour]

/remove-label lead-opted-in

[salehsedghpour]

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]

At 1.30, it won't make any changes.