Closed poblin-orange closed 3 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/176153788
The labels on this github issue will be updated when the story is started.
This issue was marked as Stale
because it has been open for 21 days without any activity. If no activity takes place in the coming 7 days it will automatically be close. To prevent this from happening remove the Stale
label or comment below.
This issue was closed because it has been labeled Stale
for 7 days without subsequent activity. Feel free to re-open this issue at any time by commenting below.
As of v44, the openstack cpi offers a way to set up a single VRRP VIP, with the allowed_adress_pair.
The CPI checks:
This works perfectly, typically with haproxy bosh release and its keepalived implementation https://github.com/cloudfoundry-incubator/haproxy-boshrelease/tree/master/jobs/keepalived
However, the single vip limitation is blocking if we want to host x vip on z vms (with x >>> z).
Openstack allows setting a set if addresse pairs, even subnet range on some implementations. The CPI should provide a way to allow multiple vips on an instance group.
(typical use case: 1 bosh k8s cluster, with metallb installed to provide x VIPs)