-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
False
-
None
-
False
-
Not Selected
-
-
-
-
Hello Team, one of the customers wants to modify the virtual_router_id for API and Ingress in the IPI cluster post-installation due to the following requirements.
we want to control the router IDs generated for keepalived because our OpenShift clusters are hosted on a L2 VXLAN fabric with BGP-EVPN underneath and we have to make sure the MAC addresses for the VRRP instances are unique fabric-wide. How do we override the virtual_router_id for Ingress and API on a per-cluster basis?
Currently, the virtual_router_id gets configured automatically.
> ./oc rsh keepalived-ci-ln-hf9b9ht-c1627-z2d4k-master-0Defaulted container "keepalived" out of: keepalived, keepalived-monitor, render-config-keepalived (init)sh-4.4# sh-4.4# sh-4.4# cat /etc/keepalived/keepalived.conf | grep -i virtual_router_id -A5 -B5 vrrp_instance ci-ln-hf9b9ht-c1627_API_0 { state BACKUP interface br-ex virtual_router_id 82 priority 40 advert_int 1 unicast_src_ip 10.38.x.x unicast_peer {-- vrrp_instance ci-ln-hf9b9ht-c1627_INGRESS_0 { state BACKUP interface br-ex virtual_router_id 113 priority 20 advert_int 1 unicast_src_ip 10.38.x.x unicast_peer {
