Support externalTrafficPolicy: Local in LoadBalancerPublishingStrategy

[freedge]

hypershift create cluster kubevirt renders spec:

  - service: APIServer
    servicePublishingStrategy:
      type: LoadBalancer

that ends up creating a service having

  externalTrafficPolicy: Cluster

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

[davidvossel]

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

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.

Note that traffic sent to an External IP or LoadBalancer IP from within the cluster will always get "Cluster" semantics

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale