Is your feature request related to a problem? Please describe.
Current issue: I have an RKE2 Cluster that I am deploying and it needs to interact with multiple networks on separate interfaces that will be segregated networks. We have been testing kube-vip to enable HA without extra external load balancing.
Describe the solution you'd like
Enable kube-vip to use a statically assigned IP for multiple interfaces and networks.
Describe alternatives you've considered
We have considered using external loadbalancing services however we are trying to limit the amount of overhead and requirements for our system, and would prefer to use built in components of kube-vip and nginx to handle this.
Additional context
example:
We have a 3 controller 3 worker cluster deployed on ubuntu 22.04 and on each we have the following interfaces with an IP from that subnet assigned.
eno1: Subnet 10.10.1.0/29 (kube-vip is on this interface with a static ip)
eno2: Subnet 10.10.1.8/29
eno3 Subnet 10.10.1.16/29
There is a network device that is segregated and can only talk on eno2 subnet, it cannot handle inputting multiple IPs to reach the same service hosted on the cluster, so we would like to use a single IP ingress with kube-vip to then balance that to the cluster.
Is your feature request related to a problem? Please describe. Current issue: I have an RKE2 Cluster that I am deploying and it needs to interact with multiple networks on separate interfaces that will be segregated networks. We have been testing kube-vip to enable HA without extra external load balancing.
Describe the solution you'd like Enable kube-vip to use a statically assigned IP for multiple interfaces and networks.
Describe alternatives you've considered We have considered using external loadbalancing services however we are trying to limit the amount of overhead and requirements for our system, and would prefer to use built in components of kube-vip and nginx to handle this.
Additional context example: We have a 3 controller 3 worker cluster deployed on ubuntu 22.04 and on each we have the following interfaces with an IP from that subnet assigned. eno1: Subnet 10.10.1.0/29 (kube-vip is on this interface with a static ip) eno2: Subnet 10.10.1.8/29 eno3 Subnet 10.10.1.16/29
There is a network device that is segregated and can only talk on eno2 subnet, it cannot handle inputting multiple IPs to reach the same service hosted on the cluster, so we would like to use a single IP ingress with kube-vip to then balance that to the cluster.