Topology Aware Subsetting

[robscott]

Enhancement Description

• One-line enhancement description (can be used as a release note): Enabling simple per-service topology aware routing configuration.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/2004-topology-aware-subsetting
• Discussion Link: https://groups.google.com/g/kubernetes-sig-network/c/wXd1D_fKjqU/m/QnStObQRBAAJ
• Primary contact (assignee): @robscott
• Responsible SIGs: sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target 1.20
  • Beta release target 1.21
  • Stable release target 1.24

This is an evolution of #536. I think this is different enough that it deserves a new KEP + issue, but I'm open to feedback on that.

[robscott]

/sig network

[robscott]

/assign

[kikisdeliveryservice]

Thanks for this, as a reminder by Enhancements Freeze (Oct 6th), in order to be included in the release:

• The KEP must be merged in an implementable state
• The KEP must have test plans
• The KEP must have graduation criteria.

/milestone v1.20

[kikisdeliveryservice]

FTR: Double checked the inflight PR and it meets the above criteria (and wow those test plans!!!). It just needs to merge by next week Tuesday October 6th

[mzohreva]

It would be useful to support same-node as well. A typical use case for same-node: Prefer is a database service. Application Pods would prefer to use the co-located database endpoint if possible.

Also, it would be useful to provide an option for advanced users to have more control over when traffic spills over to other regions. The current proposal makes it hard to reason about when spill over happens without knowing the details of the heuristics used.

[robscott]

@mzohreva Thanks for the feedback! Do you mind commenting on #2005 so we can keep all feedback in one place?

[kikisdeliveryservice]

@robscott just as a reminder, your PR (#2005 ) needs to merge by EOD PST tomorrow October 6th to be included in the 1.20 Release. After that time you will need to request an exception.

[kikisdeliveryservice]

#2005 merged! Updating sheet now 🎉

[kikisdeliveryservice]

Hey @robscott

Please keep in mind the important upcoming dates:
Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
Thursday, Nov 12th: Week 9 - Code Freeze

As a reminder, please link all of your k/k PR as well as docs PR to this issue so we can track them.

Thanks!
Kirsten

[kcmartin]

Hello @robscott , 1.20 Docs shadow here.

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

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

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

Thank you!

[kcmartin]

Hi @robscott

The docs placeholder deadline is almost here. Please make sure to create a placeholder PR against the dev-1.20 branch in the k/website before the deadline

Also, please keep in mind the important upcoming dates:

Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
Thursday, Nov 12th: Week 9 - Code Freeze
Monday, Nov 23rd: Week 11 - Docs PR Ready for Review

As a reminder, please link all of your k/k PR as well as docs PR to this issue for the release team to track.

[robscott]

Hey @kcmartin and @kikisdeliveryservice, unfortunately I don't think I'll have enough time to get this in for the 1.20 cycle. Will be trying to get it in early in 1.21 instead.

[kikisdeliveryservice]

Thanks for the update @robscott

[robscott]

KEP has been updated: #2153

[robscott]

PR for 1.21 release cycle: #2355

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale