feat: Support spec.trafficDistribution for service #324
+11
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
spec.trafficDistribution field for Kubernetes Services provides fine-grained control over how traffic is distributed to service endpoints. trafficDistribution field became stable in Kubernetes 1.33, allowing administrators to specify traffic routing policies such as PreferClose, which prioritizes endpoints in the same zone or region as the client, reducing cross-zone network latency and data transfer costs.
Changes