Kube-proxy improved ingress connectivity reliability

[alexanderConstantinescu]

Enhancement Description

• One-line enhancement description (can be used as a release note): Improve the reliability of ingress connectivity serviced by Kube-proxy
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/3836-kube-proxy-improved-ingress-connectivity-reliability
• Discussion Link:
• Primary contact (assignee): @alexanderConstantinescu
• Responsible SIGs: sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.28
  • Beta release target (x.y): 1.30
  • Stable release target (x.y): 1.31
• [x] Alpha
  • [x] KEP (k/enhancements) update PR(s):
  • https://github.com/kubernetes/enhancements/pull/3837
  • [x] Code (k/k) update PR(s):
  • https://github.com/kubernetes/kubernetes/pull/116470
  • [ ] Docs (k/website) update PR(s):
• [x] Beta
  • [x] KEP (k/enhancements) update PR(s):
  • https://github.com/kubernetes/enhancements/pull/4258,
  • [x] Code (k/k) update PR(s):
  • https://github.com/kubernetes/kubernetes/pull/122914
  • [x] Docs (k/website) update(s):
  • https://github.com/kubernetes/website/pull/45678
• [x] Stable
  • [x] KEP (k/enhancements) update PR(s):
  • https://github.com/kubernetes/enhancements/pull/4656
  • [x] Code (k/k) update PR(s):
  • https://github.com/kubernetes/kubernetes/pull/125082
  • [ ] Docs (k/website) update(s):

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

/sig-network /cc @thockin @danwinship

[alexanderConstantinescu]

/sig network

[marosset]

This enhancement meets all the requirements for inclusion in v1.27 and is now tracked for the release!

[marosset]

Hi @alexanderConstantinescu :wave:,

Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.

Please ensure the following items are completed:

• [ ] All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• [ ] All PRs are fully merged by the code freeze deadline.

Please let me know if there are any other PRs in k/k I should be tracking for this KEP.

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

[taniaduggal]

Hi @alexanderConstantinescu 👋 , I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release. Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release. Please feel free to reach out with any questions. Thanks!

[marosset]

Unfortunately the implementation PRs associated with this enhancement have not merged by code-freeze so this enhancement is getting removed from the release.

If you would like to file an exception please see https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md

/milestone clear /remove-label tracked/yes /label tracked/no

[thockin]

@alexanderConstantinescu https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/3836-kube-proxy-improved-ingress-connectivity-reliability/kep.yaml still says Alpha and needs a PRR touch to move to beta

[alexanderConstantinescu]

Thanks for the reminder, sorry for being late. Here's the PR: https://github.com/kubernetes/enhancements/pull/4087

[aramase]

Hello @alexanderConstantinescu 👋, Enhancements team here.

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

This enhancement is targeting for stage alpha for 1.28 (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.28
• [ ] KEP readme has a updated detailed test plan section filled out
• [ ] KEP readme has up to date graduation criteria
• [ ] KEP has a production readiness review that has been completed and merged into k/enhancements.

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

[Atharva-Shinde]

Hey @alexanderConstantinescu

This is a nit that needs to be addressed: Add the acknowledgement under the Test Plan section.

I won't decline this KEP for the Enhancements freeze because of this change but would be great to get a PR ready addressing them. The status of this enhancement is marked as tracked. Please keep the issue description up-to-date with appropriate stages as well. Thank you :)

[alexanderConstantinescu]

@Atharva-Shinde : Addressed for both 3458 and 3836 with https://github.com/kubernetes/enhancements/pull/4095

[katcosgrove]

Hello @alexanderConstantinescu! 1.28 Docs Shadow here.

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

If so, please follows the steps here to open a PR against dev-1.28 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 20th July 2023.

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

Thank you!

[alexanderConstantinescu]

Sorry for the late reply @katcosgrove :

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

No, it does not.

[aramase]

Hey again @alexanderConstantinescu:wave:

Just checking in as we approach Code freeze at 01:00 UTC Friday, 19th July 2023 .

Here’s the enhancement’s state for the upcoming code freeze:

• [x] All the PRs that are related to your enhancement are linked in the above issue description (for tracking purposes). This includes code, tests, and documentation related PR/s.
• [x] All code related PR/s are merged or are in merge-ready state ( i.e they have approved and lgtm labels applied) by the code freeze deadline. This includes any tests related PR/s too.
  • https://github.com/kubernetes/kubernetes/pull/116470

If there are any other k/k related PR(s) that we should be tracking for this KEP please link them in the issue description above.

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

[Atharva-Shinde]

Hey @alexanderConstantinescu 👋 Enhancements Lead here, With https://github.com/kubernetes/kubernetes/pull/116470 merged as per the issue description, this enhancement is now tracked for v1.28 Code Freeze. Thanks!

[thockin]

I am tracking this for beta in 1.29 - is that correct?

[alexanderConstantinescu]

I am tracking this for beta in 1.29 - is that correct?

Yes, that is correct.

[npolshakova]

Hello @alexanderConstantinescu! 👋 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 beta 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.
• [ ] 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
• [ ] KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

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

• Update the latest-milestone to 1.29
• Have a completed PRR review and merged into k/enhancements for the beta stage

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!

[npolshakova]

Hi @alexanderConstantinescu, just checking in once more as we approach the 1.29 enhancement freeze deadline this week on 01:00 UTC, Friday, 6th October, 2023. The status of this enhancement is marked as at risk for enhancement freeze.

It looks like https://github.com/kubernetes/enhancements/pull/4258 will address most of the requirements. Let me know if I missed anything. Thanks!

[alexanderConstantinescu]

It looks like https://github.com/kubernetes/enhancements/pull/4258 will address most of the requirements. Let me know if I missed anything. Thanks!

Hi @npolshakova ! That PR has merged and should fulfill all necessary requirements for progressing this KEP to the next phase. Let me know if anything is missing, but this KEP should be ready now for the next Kube release.

[npolshakova]

Looks good! This enhancement is now tracked for enhancement freeze. 🚀

[harshitasao]

Hi @alexanderConstantinescu :wave:, 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!

[npolshakova]

Hey again @alexanderConstantinescu 👋, 1.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.

Please update the Issue description to include all the related PRs of this KEP (including https://github.com/kubernetes/enhancements/pull/4258) under a new beta section in the Github Issue description. The status for this KEP is currently at risk for code freeze.

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!

[kcmartin]

Hi @alexanderConstantinescu ! 👋 from the v1.29 Release Team-Communications! We would like to check if you have any plans to publish a blog for this KEP regarding new features, removals, and deprecations for this release.

If so, you need to open a PR placeholder in the website repository. The deadline will be on Tuesday 14th November 2023 (after the Docs deadline PR ready for review)

Here's the 1.29 Calendar

[npolshakova]

Hello @alexanderConstantinescu 👋, 1.29 Enhancements team here.

With https://github.com/kubernetes/enhancements/pull/4258 merged, all the tracked implementation(code related) PRs are merged as per the issue description and 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. Please let me know if there are any test PRs we should track. Thanks!

[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

[thockin]

Pinging this after sig-net - let's decide if this moves to beta in 1.30

[tjons]

Hello @alexanderConstantinescu 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on Friday, February 9th, 2024 at 02:00 UTC.

This enhancement is targeting for stage beta for 1.30 (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.30. 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).

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

• [x] Complete the PRR review process and merge it into k/enhancements.

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!

[alexanderConstantinescu]

@tjons : I made a mistake in the last release and got a prr-review for Beta, but forgot to update the code afterwards. In this release we're only updating the code and the prr-review file already exists, see: https://github.com/kubernetes/enhancements/blob/master/keps/prod-readiness/sig-network/3836.yaml

Is this fine?

[tjons]

@alexanderConstantinescu thanks for the update! This should be fine... With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀

[chanieljdan]

Hi @alexanderConstantinescu and @thockin 👋, 1.30 Docs Shadow 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!

[a-mccarthy]

Hi @alexander-demicev and @thockin,

👋 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

[chanieljdan]

Hi @alexanderConstantinescu and @thockin 👋, 1.30 Docs Shadow 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!

Hi @alexanderConstantinescu and @thockin 👋, could you review the above before the placeholder deadline tonight? Thanks!

[alexanderConstantinescu]

@chanieljdan : sorry for the delay! It was indeed agreed that this enhancement should result in a document written in https://kubernetes.io/docs/concepts/. Here's a placeholder PR I created for this: https://github.com/kubernetes/website/pull/45290

What is the deadline for the final docs PR to merge for 1.30?

[tjons]

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

• [x] All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• [x] 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 linked PR is already approved and merged and has the appropriate labels, so I believe you are good to go. 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!

[thockin]

@alexanderConstantinescu GA in 31?

[sreeram-venkitesh]

Hi @alexanderConstantinescu! v1.31 Enhancements lead here 👋🏼

I'm removing the lead-opted-in label for now. If you wish to progress this enhancement in v1.31, please have the SIG lead opt-in your enhancement by adding the lead-opted-in label and set the milestone to v1.31 before the Production Readiness Review Freeze. Please let me know if you have any questions.

/remove-label lead-opted-in

[aojea]

@alexanderConstantinescu @thockin this is just removing the flag during this release, isn't it?

we should opt in then

[thockin]

No, this one is Beta->GA

[aojea]

No, this one is Beta->GA

oh, wanted to mean that there is no much work and we should opt-in

[thockin]

Agree, I just want @alexanderConstantinescu to ACK

[alexanderConstantinescu]

Yes, 1.31 is Beta -> Stable and to the best of my knowledge the graduation criteria defined on the KEP are already satisfied, so it's a matter of "filling out the paperwork" (updating the KEP/feature gates)

[thockin]

ACK!

[ArkaSaha30]

Hello @thockin 👋, 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 stage stable for v1.31 (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: v1.31. 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). 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 so that the PRR team has enough time to review your KEP before the enhancements freeze.

For this KEP, it would be good to update the following:

• [ ] Implementation history in the KEP README

Other than this, all the KEP requirements are in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

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!

[ArkaSaha30]

/stage stable

[Princesso]

Hello @thockin :wave:, 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!

[mbianchidev]

Heey @thockin , @alexanderConstantinescu

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

Hello @thockin 👋, 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 @thockin, @alexanderConstantinescu, gentle reminder to raise a doc placeholder PR for this enhancement before Thursday June 27, 2024 18:00 PDT.

[mbianchidev]

Heey @thockin , @alexanderConstantinescu

👋 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 :eyes: )

[natalisucks]

Hello @thockin 👋, 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 @thockin, @alexanderConstantinescu, gentle reminder to raise a doc placeholder PR for this enhancement before Thursday June 27, 2024 18:00 PDT.

Howdy @thockin, @alexanderConstantinescu, SIG Docs co-chair here 👋 I wanted to add another reminder about the docs deadline for this enhancement: updating feature gates qualifies as requiring documentation as far as Release Docs is concerned, so please check out @Princesso's reminder above to ensure you meet the deadline today