Topology Aware Routing

[robscott]

Enhancement Description

• One-line enhancement description (can be used as a release note): EndpointSlice controller can be configured to provide topology aware hints that will enable simple topology aware routing.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/2433-topology-aware-hints
• Discussion Link: https://docs.google.com/document/d/1ZzUoFY1SrdjVefl7gVOJZJLt1I1LHttw8pcX95nlgMY/edit
• Primary contact (assignee): @gauravkghildiyal
• Responsible SIGs: sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): v1.21
  • Beta release target (x.y): v1.23
  • Stable release target (x.y): v1.33
• Alpha
  • KEP (k/enhancements) update PR(s): KEP 2004: Evolving Topology Aware Routing for Services #2005
  • Code (k/k) update PR(s):
  • Docs (k/website) update PR(s):
• Beta
  • KEP (k/enhancements) update PR(s): KEP-2433: Removing traffic policy interoperability as beta graduation requirement #3043
  • Code (k/k) update PR(s):
    • 1.23 default false Graduate TopologyAwareHints feature gate to beta kubernetes#106433
    • 1.24 default true Updating TopologyAwareHints feature gate to be on by default kubernetes#108747
  • Docs (k/website) update PR(s): Mark that TopologyAwareHints feature is default on in 1.24 website#32361
• GA
  • KEP (k/enhancements) update PR(s):
    • 1.26 Updating Topology Aware Hints KEP with GA Graduation Criteria #3572
    • 1.27 KEP-2413: Graduate SeccompDefault to stable #3718, KEP-2433 Topology Aware Hints: Adding SameZone heuristic and other tweaks #3765
    • 1.28 KEP-2433: add new heuristic to topology routing #4003
    • 1.29-1.30 KEP-2433: Bumping stable target to 1.30 #4284
  • Code (k/k) update PR(s):
    • 1.29 TopologyAwareHints: Take lock in HasPopulatedHints kubernetes#118189
    • 1.33 Promote TopologyAwareHints feature-gate to GA kubernetes#130742
  • Docs (k/website) update PR(s):

/sig network

[robscott]

/assign

[kendallroden]

Hi @robscott ,
Since your Enhancement is scheduled to be in 1.21, please keep in mind the important upcoming dates:

• Tuesday, March 9th: Week 9 - Code Freeze
• Tuesday, March 16th: Week 10 - Docs Placeholder PR deadline
  • If this enhancement requires new docs or modification to existing docs, please follow the steps in the Open a placeholder PR doc to open a PR against k/website repo.
• As a reminder, please link all of your k/k PR(s) and k/website PR(s) to this issue so we can track them.

Thanks!

[JornShen]

@robscott What' the develop process of this feature? I am interested in it. Is there something I can help to do ? :)

[robscott]

Hey @JornShen thanks for checking in! If you have time, I'd really appreciate any review or testing of my related PR: kubernetes/kubernetes#99522.

[kendallroden]

Hey @robscott! I know you are aware based on other enhancement work that code freeze is coming up on March 9th EOD PST and if any PRs are not merged by the deadline, you'll have to request an exception! Please also keep in mind that if this enhancement requires new docs or modification to existing docs, you'll need to follow the steps in the Open a placeholder PR doc to open a PR against k/website repo by March 16th EOD PST
Thanks!

[annajung]

Hi @robscott, with kubernetes/kubernetes#99522 merged in, we will mark this as code complete for 1.21 release.

[reylejano]

Hello @robscott , 1.21 Docs lead here.
Does this enhancement work planned for 1.21 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.21 branch in the k/website repo. This PR can be just a placeholder at this time and must be created by March 16 EOD PST
Also take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!

[robscott]

Hey @reylejano, thanks for checking in! This will require some significant docs additions. I'll make sure to have a docs PR ready before that deadline.