-
Notifications
You must be signed in to change notification settings - Fork 298
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
Support externalTrafficPolicy: Local in LoadBalancerPublishingStrategy #3592
Comments
Yes, I see how that could benefit the Agent platform. I'm unsure if the KubeVirt platform would benefit much from this though. In that case, the bulk of the api server traffic is going to come from the VMs acting as worker nodes which in most cases will result in internal traffic. Per the externalTrafficPolicy documentation, that internal traffic would default to Cluster even if we set it to Local.
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
hypershift create cluster kubevirt
renders spec:that ends up creating a service having
It would be great if it could be Local instead, so that the traffic is routed to the right node
https://metallb.universe.tf/usage/#local-traffic-policy-1
The text was updated successfully, but these errors were encountered: