CAPO: users sometimes delete the VIP port

Today the Neutron port for the Cluster VIP appears as

$ openstack port list
+--------------------------+-----------------------------------------+-------------------+------+--------+
| ID                       | Name                                    | MAC Address       | .... | Status |
+--------------------------+-----------------------------------------+-------------------+------+--------+
...
| 2ddac4d28-8750-a869cca72 | management-cluster-..-port-tgubj72hvasw | fa:16:3e:c8:5e:f9 | .... | DOWN   |
...
+--------------------------+-----------------------------------------+-------------------+------+--------+

Our users ...

  • ...easily confuse this with a port allocated by Cluster API
  • ... and given that it is DOWN, think that it isn't used anymore ... and they clean it up !

This situation is problematic:

  • there is no easy path to put it back in the HeatStack and the capo-cluster-resources ConfigMap
  • the IP could be reused by some other Sylva stack on the same network
Edited Mar 20, 2025 by Thomas Morin
Assignee Loading
Time tracking Loading