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: KEP-3836: Improve Kube-proxy ingress connectivity reliability #3837
• Discussion Link:
• Primary contact (assignee): @alexanderConstantinescu
• Responsible SIGs: sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y):
  • Beta release target (x.y):
  • Stable release target (x.y): v1.28
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-3836: Improve Kube-proxy ingress connectivity reliability #3837
  • Code (k/k) update PR(s):
    • [Kube-proxy]: Implement KEP-3836 kubernetes#116470
  • Docs (k/website) update PR(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 👋,

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