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

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!

[chanieljdan]

Hi @gauravkghildiyal 👋, 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 @gauravkghildiyal,

👋 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 @gauravkghildiyal 👋, 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 @gauravkghildiyal 👋, just wanted to follow up here, if you could review before the placeholder deadline tomorrow that would be great!

[gauravkghildiyal]

Thanks for the reminder @chanieljdan . I've created the draft PR at kubernetes/website#45276 and updated the issue description.

[AnaMMedina21]

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

• 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.

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):

• Introduce trafficDistribution field for Kubernetes Services kubernetes#123487

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!

[gauravkghildiyal]

Hi @AnaMMedina21 -- Update: The code changes have been merged.

[salehsedghpour]

Hello @gauravkghildiyal 👋 , Enhancements team here.

With all the implementation(code related) PRs merged as per the issue description:

• Introduce trafficDistribution field for Kubernetes Services kubernetes#123487

This enhancement is now marked as tracked for code freeze for the v1.30 Code Freeze!

[gauravkghildiyal]

FYI for someone monitoring, the docs are ready for review at kubernetes/website#45276. Thanks!

[lzhecheng]

Hello @gauravkghildiyal, is this feature completed? Does it need code change in CNI side? Thanks.

I enable feature gate in apiserver, kcm and kube-proxy but it still doesn't work.

[gauravkghildiyal]

Hi @lzhecheng, yes as far as I evaluated, this should not be requiring any more changes if you are using kube-proxy. Let's connect over slack if this needs discussion (would prefer to not use this issue for debugging)

[sreeram-venkitesh]

/stage beta

[prianna]

Hello @gauravkghildiyal 👋, 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 beta for v1.31 (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.31. 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 for the targeted stage 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 of Thursday 6th June 2024 so that the PRR team has enough time to review your KEP.

For this KEP, it looks like we still need to do the following:

• Update KEP to target latest-milestone: v1.31 and beta stage
• Update graduation criteria
• PRR for graduation to beta

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.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[gauravkghildiyal]

Thanks @prianna ! Updated KEP with relevant changes that can be tracked: #4659.

[gauravkghildiyal]

Hi @prianna! The KEP changes (#4659) have merged and I hope that covers all the requirements.

[prianna]

Hey folks, thank you for getting #4659 merged. 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.31. 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 submitted a production readiness review request for approval and has a reviewer assigned.
• 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!

[Princesso]

Hello @gauravkghildiyal 👋, 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]

Hello there @gauravkghildiyal

👋 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 @gauravkghildiyal 👋, 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!

@gauravkghildiyal, gentle reminder to open a draft PR for the enhancement before Thursday, June 27, 2024.

[mbianchidev]

Hello there @gauravkghildiyal

👋 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 👀 )

[gauravkghildiyal]

Hi @Princesso -- Here is the draft PR for the docs update; I've also updated the description. kubernetes/website#46973

---

Hi @mbianchidev -- Thanks for the reminder. I don't think we'll be needing a blog post with this release so I'll opt-out

[prianna]

Hey again @gauravkghildiyal 👋 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.

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.

With all the implementation(code related) PRs merged as per the issue description:

• Promote ServiceTrafficDistribution feature-gate to beta and enable by default. Also add missing integration tests. kubernetes#125838

This enhancement is now marked as tracked for code freeze for the 1.31 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!

[tjons]

Hi, enhancements lead here - I inadvertently added this to the 1.32 tracking board 😀. Please readd it if you wish to progress this enhancement in 1.32.

/remove-label lead-opted-in

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale