No ARP reply in case of HAproxy vIP and EgressIP assigned to the same INFRA node
Issue
- In a scenario where the HAproxy
Ingress vIP
(floating IP address associated to the OpenShift Application Domain) is assigned to the same INFRA node where also theEgressIP
of theopenshift-gitops (ArgoCD)
is allocated, any ARP request for theEgressIP
address (ARP request sent from the node that is hosting the HAproxyIngress vIP
) won't be answered at all. - As result of the behaviour above described, the authentication in openshift-gitops (ArgoCD integrated with OpenShift) will systematically fail because from the INFRA node isn't possible to resolve the EgressIP.
Environment
- Red Hat OpenShift 4 with the OVN-Kubernetes Container Network Interface (CNI) plugin.
- openshift-gitops operator 1.7.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.