feat(hubble): Add trafficDistribution
field support for Kubernetes 1.31+
#1686
+18
−0
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.
Description
Add trafficDistribution field support to Hubble services (excluding DaemonSet-connected services) with Kubernetes version compatibility check (≥1.31). This provides better performance and reliability than annotation-based topologyAwareRouting by being natively integrated into the Service API.
Changes:
Usage
Retina administrators can now set hubble.relay.service.trafficDistribution: PreferClose or hubble.ui.service.trafficDistribution: PreferClose in their values to enable topology-aware routing with improved performance characteristics.
Related Issue
Checklist
git commit -S -s ...
). See this documentation on signing commits.Screenshots (if applicable) or Testing Completed
Please add any relevant screenshots or GIFs to showcase the changes made.
Additional Notes
Why trafficDistribution over topologyAwareRouting?
The trafficDistribution field is recommended over topologyAwareRouting annotations as it provides native Kubernetes Service API integration with better performance and reliability characteristics. This field is available in Kubernetes 1.31+ and offers more granular control over traffic routing behavior compared to the annotation-based approach.
Please refer to the CONTRIBUTING.md file for more information on how to contribute to this project.