Graduate the kube-proxy ComponentConfig

[luxas]

• One-line enhancement description (can be used as a release note): Introduce v1alpha2 kube-proxy component config version
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/784-kube-proxy-component-config
• Discussion Link: Introduce v1alpha2 kube proxy configuration kubernetes#121830
• Primary contact (assignee): @aroradaman
• Responsible SIGs: sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.32
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-784: update template #4311, KEP-784: Update design-details #4337, KEP 784: Update Milestones #4732, Kube proxy config v1alpha2 milestone and design #4886
  • Code (k/k) update PR(s):
    • 1.31 kube-proxy: internal config: add Linux and Windows section kubernetes#126072
    • 1.31 Kube proxy refactor internal config kubernetes#126293
    • 1.32 kube-proxy: internal config: refactor HealthzAddress and MetricsAddress  kubernetes#126889
    • re: kube-proxy: internal config: refactor HealthzAddress and MetricsAddress  kubernetes#127930
    • kube-proxy: internal config: refactor BindAddress kubernetes#126258
  • Docs (k/website) update PR(s): [WIP] KEP-784 website#47001

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

[sttts]

We need a thorough API review of the kube-proxy component config in the light of unifying them for all components. Moving what we have to beta in the 1.14 time frame feels like rushing in the light of us having just started with component-base.

[claurence]

@luxas I don't see a KEP for this issue links in the description. I'm removing it from the 1.14 milestone - to have it added back please file an exception request.

[rosti]

I am giving this a try.
/assign

[kacole2]

@luxas @rosti I'm the enhancement lead for 1.15. I don't see a KEP filed for this enhancement and per the guidelines, all enhancements will require one. Please let me know if this issue will have any work involved for this release cycle and update the original post reflect it. Thanks!

[rosti]

@kacole2 I am a bit skeptical for a KEP in this release cycle, however if we manage to put something before enhancements freeze for 1.15 then we'll ping you.

[rosti]

Initial proposal doc.
This is shared with WG Component Standard, SIG Network, SIG Windows, SIG API Machinery and SIG Cluster Lifecycle. If someone has trouble accessing it, ping me.

[mtaufen]

@rosti thanks for picking this up! The common vs. local and per-platform config problems have needed someone who can really focus on them for a while, and I haven't been able to dedicate enough time lately. So I'm grateful someone's looking at this :). This is critical to the future of the componentconfig effort.

[mtaufen]

I left some comments on your doc.

[mtaufen]

@vllry, I heard you're also going to be working on kube-proxy componentconfig, wanted to make sure you see this.

[stealthybox]

@rosti, shall we tag this /w 1.16 and update KEP #1104?

[alejandrox1]

Moving this to the 1.16 milestone to tackle during the next release
/milestone v1.16

[neolit123]

IMO we should have k/enhancements issues that track full graduation of APIs. from alpha->GA instead of separate ones for beta or GA.

[rosti]

If the KEP merges we can have an alpha version released before the end of the cycle, so I think, that it's appropriate to have it in 1.16.

[mrbobbytables]

Hey there @luxas, I'm one of the 1.16 Enhancement Shadows. Looks like you're on track for v1.16 :)

As a general reminder, the KEP must be merged and in an implementable state with Graduation Criteria explaining each alpha/beta/stable stages requirements.

Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.

Thank you.

[sreeram-venkitesh]

/milestone clear

[sreeram-venkitesh]

Marking the KEP as tracked for enhancements freeze since the exception request was approved and with #4732 merged.

[mbianchidev]

Hey @luxas

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

Hello @aroradaman 👋, 1.31 Docs Lead here. Does this enhancement work planned for 1.31 require any new docs or modification to existing docs? If so, please follow 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 familiarised with the docs requirement for the release. Thank you!

hi @aroradaman, gentle reminder to open a draft PR for this enhancement before Thursday June 27, 2024.

[mbianchidev]

Hey @luxas

👋 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.

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 👀 )

[ArkaSaha30]

Hey again @aroradaman 👋, 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:

• 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.

Regarding this enhancement, it appears that there is currently one PR (kubernetes/kubernetes#121830) in k/k repository.

For this KEP, we would need to do the following:

• Ensure the current merge conflict in the PR is resolved
• Ensure any additional PRs to k/k repos related to this KEP are linked in the above issue description for tracking purposes).
• Ensure all PRs are prepared for merging (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

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

The status of this enhancement is marked as at risk for code freeze.

[sreeram-venkitesh]

/milestone v1.31

[ArkaSaha30]

Hey again @aroradaman 👋, 1.31 Enhancements team here,

Just a quick friendly reminder as we approach code freeze in about 2 days, at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.

The current status of this enhancement is marked as at risk for code freeze. A few requirements mentioned in the comment #784 (comment) still need to be completed.

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

[sreeram-venkitesh]

Hello @aroradaman 👋 v1.31 Enhancements team here,

Unfortunately, the implementation (code related) PR(s) associated with this enhancement is not in the merge-ready state by code-freeze and hence this enhancement is now removed from the v1.31 milestone.

If you still wish to progress this enhancement in v1.31, please file an exception request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks!

/milestone clear

[thockin]

@aroradaman shooting for 1.32?

[aroradaman]

@aroradaman shooting for 1.32?

Yes, we are almost there 🤞

[jenshu]

Hello @aroradaman 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

This enhancement is targeting for stage alpha for v1.32 (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: v1.32.
• 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). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 3rd October 2024 so that the PRR team has enough time to review your KEP.

For this KEP, we would just need to update the following:

• The kep.yaml needs to have the latest-milestone updated to v1.32

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.

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

[aroradaman]

/retitle Graduate the kube-proxy ComponentConfig

[jenshu]

Hi @aroradaman I see that the kep.yaml has been updated, so everything looks good for enhancements freeze! I'm going to update the status to tracked

[hacktivist123]

Hello @aroradaman 👋 1.32 Docs Shadow here.

Does this enhancement work planned for 1.32 require any new docs or modifications to existing docs?
If so, please follow the steps here to open a PR against the dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, October 24th 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!

[hacktivist123]

Hello, @aroradaman 👋 1.32 Docs Shadow here.

This is just a reminder to open a placeholder PR against dev-1.32 branch in the k/website repo for this (steps available here) for this KEP if it requires new or modifications to existing docs:

The deadline for this is Thursday, Oct 24 at 18:00 PDT.

Thanks! 🚀

[wrkode]

👋 Hi there, William here from v1.32 Comms
We'd love for you to consider writing 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 30th Oct 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.

[jenshu]

Hey again @aroradaman 👋, v1.32 Enhancements team here.

Just checking in as we approach code freeze at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 2024.

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.

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

• kube-proxy: internal config: refactor HealthzAddress and MetricsAddress  kubernetes#126889
• re: kube-proxy: internal config: refactor HealthzAddress and MetricsAddress  kubernetes#127930
  • seems this has been reverted by Revert "re: kube-proxy: internal config: refactor HealthzAddress and MetricsAddress " kubernetes#128216 and possibly reimplemented with re: re: kube-proxy: internal config: refactor HealthzAddress and MetricsAddress kubernetes#128303, can you confirm the state of this one?
• kube-proxy: internal config: refactor BindAddress kubernetes#126258

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

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!

[jenshu]

Hello @aroradaman 👋, v1.32 Enhancements team here,

Unfortunately, the implementation (code related) PR(s) associated with this enhancement are not in the merge-ready state by code-freeze and hence this enhancement is now removed from the v1.32 milestone.

If you still wish to progress this enhancement in v1.32, please file an exception request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks!

/milestone clear