You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using EnvoyGateway on cilium load balancer with L2 Announcements.
Cilium uses leases to assign the IP to a node, as L2 LB is more a fail over IP than a real load balancer.
When there is no envoy(gateway) pod on this node, the gateway is not reachable on the external/LB IP.
Our current current workaround is setting envoyDeployment.replicas to the dataplane's node count.
One way to address this would be to run envoy as DaemonSet, simple and efficient, but we may not want to run EnvoyGateway on all/some nodes.
A better way would be to automatically run an Envoy pod on all nodes matching the corresponding CiliumL2AnnouncementPolicy CR's selector.
We are using EnvoyGateway on cilium load balancer with L2 Announcements.
Cilium uses leases to assign the IP to a node, as L2 LB is more a fail over IP than a real load balancer.
When there is no envoy(gateway) pod on this node, the gateway is not reachable on the external/LB IP.
Our current current workaround is setting
envoyDeployment.replicas
to the dataplane's node count.One way to address this would be to run envoy as DaemonSet, simple and efficient, but we may not want to run EnvoyGateway on all/some nodes.
A better way would be to automatically run an Envoy pod on all nodes matching the corresponding
CiliumL2AnnouncementPolicy
CR's selector.https://docs.cilium.io/en/stable/network/l2-announcements/
The text was updated successfully, but these errors were encountered: