How to apply symmetric routing for Metallb L2 services via multiple interfaces in RHOCP4?
Issue
- The Metallb services advertised via L2 method using a not primary interface seem to be affected by asymmetric routing.
- Why is the communication from external networks not getting routed properly once the Metallb service assigns
IPs
from secondary interface? - The outgoing packets against LoadBalancer services are not being sent by RHOCP node using same secondary interface.
- Why is needed to configure static routes in RHOCP node to reply the
LoadBalancer
requests against Metallb services using multiple network interfaces?
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 4
- Kubernetes NMState Operator
- MetalLB operator
- NetworkType: OVNKubernetes
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.