Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate status.nodeInfo.kubeProxyVersion field #4004

Open
8 tasks done
HirazawaUi opened this issue May 15, 2023 · 15 comments
Open
8 tasks done

Deprecate status.nodeInfo.kubeProxyVersion field #4004

HirazawaUi opened this issue May 15, 2023 · 15 comments
Assignees
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node.
Milestone

Comments

@HirazawaUi
Copy link
Contributor

HirazawaUi commented May 15, 2023

Enhancement Description

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

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label May 15, 2023
@HirazawaUi
Copy link
Contributor Author

/sig node
/cc @danwinship
/assign

@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 15, 2023
@HirazawaUi
Copy link
Contributor Author

/cc @thockin

@SergeyKanzhelev
Copy link
Member

/milestone v1.28

@k8s-ci-robot k8s-ci-robot added this to the v1.28 milestone May 26, 2023
@thockin thockin added the sig/network Categorizes an issue or PR as relevant to SIG Network. label Sep 27, 2023
@thockin
Copy link
Member

thockin commented Sep 27, 2023

What the staus on this? Alpha in 29?

@HirazawaUi
Copy link
Contributor Author

What the staus on this? Alpha in 29?

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

@SergeyKanzhelev
Copy link
Member

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

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.28, v1.29 Sep 27, 2023
@k8s-ci-robot k8s-ci-robot added the lead-opted-in Denotes that an issue has been opted in to a release label Sep 27, 2023
@npolshakova
Copy link

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:

  • KEP readme using the latest template has been merged into the k/enhancements repo.
  • 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.
  • KEP readme has up-to-date graduation criteria
  • 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
Copy link

krol3 commented Oct 2, 2023

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
Copy link
Contributor Author

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

@harshitasao
Copy link

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
Copy link
Contributor Author

I have opened a placeholder PR at k/website.

@AnaMMedina21
Copy link

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 kubernetes/website#43348 and kubernetes/kubernetes#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
Copy link

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
Copy link

kcmartin commented Nov 14, 2023

@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
Copy link
Contributor Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
Status: Tracked for Code Freeze
Development

No branches or pull requests

10 participants