/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 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!

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

@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!

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,

👋 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

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!

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:

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

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:

• Introduce trafficDistribution field for Kubernetes Services kubernetes#123487

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

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)