New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Traffic Distribution for Services #4444
Comments
/assign |
Marking this opted-in, though it may or may not make the cut, let's try. |
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 Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
The status of this enhancement is marked as |
Hello @AnaMMedina21 -- the KEP PR has merged. Does this mean we are all good for 1.30? |
@gauravkghildiyal Hi!
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 |
Hi @gauravkghildiyal 👋, 1.30 Docs Shadow here. Does this enhancement work planned for 1.30 require any new docs or modification to existing docs? Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you! |
👋 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. |
Hi @gauravkghildiyal 👋, just wanted to follow up here, if you could review before the placeholder deadline tomorrow that would be great! |
Thanks for the reminder @chanieljdan . I've created the draft PR at kubernetes/website#45276 and updated the issue description. |
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:
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): Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. |
Hi @AnaMMedina21 -- Update: The code changes have been merged. |
Hello @gauravkghildiyal 👋 , Enhancements team here. With all the implementation(code related) PRs merged as per the issue description: This enhancement is now marked as |
FYI for someone monitoring, the docs are ready for review at kubernetes/website#45276. Thanks! |
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. |
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) |
Enhancement Description
trafficDistribution
field to Kubernetes Service specifications for expressing traffic routing preferences.k/enhancements
) update PR(s):k/k
) update PR(s):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
The text was updated successfully, but these errors were encountered: