-
Notifications
You must be signed in to change notification settings - Fork 370
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
Fix hint annotation implementation in AntreaProxy #6607
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Please add description that this is to be consistent with kube-proxy's behavior.
This commit is to be consistent with kube-proxy's behavior for Topology Aware Routing feature. For `service.kubernetes.io/topology-mode` hint annotation, any non-empty and non-disabled values for the annotation are acceptable to enable Topology Aware Routing for a Service. Signed-off-by: Hongliang Liu <[email protected]>
93fa7b3
to
a82c3bb
Compare
Done |
I think setting the annotation value to other values wouldn't work because endpointslice controller only adds hints when the value is |
@hongliangl let me know if my understanding is correct. |
@tnqn You are right. Only |
/skip-all |
1 similar comment
/skip-all |
@hongliangl are you going to back-port this to Antrea v2.0 and v2.1? |
No. See #6607 (comment) |
Ah, my bad, I didn't notice the label was already removed. Ignore me. |
This commit is to be consistent with kube-proxy's behavior for Topology
Aware Routing feature.
For
service.kubernetes.io/topology-mode
hint annotation, any non-emptyand non-disabled values for the annotation are acceptable to enable
Topology Aware Routing for a Service.