Added cleanup for bootstrap VM FIP in the insatller as part of the
PostDestroyer to streamline FIP creation and deletion to be done by the
installer avoiding orphan FIPs.
Before this patch, the bootstrap FIP was attached to the first available
port attached to the bootstrap server. As a consequence, the Installer
sometimes tried to attach the FIP to a port that was created on an
additional network.
With this patch, the bootstrap FIP is only attached to the bootstrap
port that exists on the cluster network.
When no external network is set on CAPO Cluster status
it's not possible to create a Floating IP for the bootstrap.
This commit fixes the issue by skipping the creation.
This is the result of the following steps:
1. Fork cluster-api-provider-openstack and revert its go.mod to Go v1.21
2. Replace the fork in the Installer's go.mod
3. Replace imports from v1alphaX to v1beta1
4. Update manifests to use the v1beta1 spec
This is created in the postprovision step, since we'll attach it once
the bootstrap machine has been created.
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
