Traffic Distribution for Services

[gauravkghildiyal]

Enhancement Description

• One-line enhancement description (can be used as a release note): Introduce a trafficDistribution field to Kubernetes Service specifications for expressing traffic routing preferences.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/4444-service-traffic-distribution
• Discussion Link:
• Primary contact (assignee): @gauravkghildiyal
• Responsible SIGs: sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): v1.30
  • Beta release target (x.y): v1.31
  • Stable release target (x.y): v1.33 (TBD)
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-4444: Routing Preference for Services #4445
  • Code (k/k) update PR(s):
    • Introduce trafficDistribution field for Kubernetes Services kubernetes#123487
    • (e2e tests) Add e2e and integration tests for Service.spec.trafficDistribution kubernetes#123812
  • Docs (k/website) update PR(s):
    • Document .spec.trafficDistribution field in Service website#45276
• Beta
  • KEP (k/enhancements) update PR(s):
    • KEP-4444: Update PRR sections for beta release targeting 1.31 #4659
  • Code (k/k) update PR(s):
    • Promote ServiceTrafficDistribution feature-gate to beta and enable by default. Also add missing integration tests. kubernetes#125838
  • Docs (k/website) update(s):
    • Docs update for k8s 1.31 regarding Service trafficDistribution website#46973
• Stable
  • KEP (k/enhancements) update PR(s):
    • KEP-4444: Graduate trafficDistribution:PreferClose to GA #5152
  • Code (k/k) update PR(s):
    • Promote ServiceTrafficDistribution feature-gate to GA and update docs with latest descriptions kubernetes#130673
  • Docs (k/website) update(s):
    • KEP-3015 PreferSameNode TrafficDistribution 1.33 website#49943

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

/sig network

[gauravkghildiyal]

/assign

[thockin]

Marking this opted-in, though it may or may not make the cut, let's try.

[AnaMMedina21]

Hello @gauravkghildiyal 👋, Enhancements team here.

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

This enhancement is targeting for stage alpha for v1.30 (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.30. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• 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:

• Waiting for KEP and PRR to get approved and merged KEP-4444: Routing Preference for Services #4445

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!

[gauravkghildiyal]

Hello @AnaMMedina21 -- the KEP PR has merged. Does this mean we are all good for 1.30?

[AnaMMedina21]

@gauravkghildiyal Hi!
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.30. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• 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).

With all the KEP requirements 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!