We have a unique constraint placed on us by a provider. We have two separate networks that are in the same VLAN. In order to make routing work correctly, the ability to set the virtual_ipaddress to match that network's subnet would be the ideal solution, ideally through a config map.
Something along the lines of:
apiVersion: v1
kind: ConfigMap
metadata:
name: vip-configmap
data:
10.0.0.10: ""
vip_cidr: 27
resulting in:
virtual_ipaddress {
10.0.0.10/27
}
inside the container's /etc/keepalived.conf, which is a valid keepalived configuration.
We have a unique constraint placed on us by a provider. We have two separate networks that are in the same VLAN. In order to make routing work correctly, the ability to set the virtual_ipaddress to match that network's subnet would be the ideal solution, ideally through a config map.
Something along the lines of:
resulting in:
inside the container's /etc/keepalived.conf, which is a valid keepalived configuration.