cluster-api-provider-openstack
cluster-api-provider-openstack copied to clipboard
**What this PR does / why we need it**: When an ExternalNetwork has multiple subnets, allow to select a subnet by id to be used for floating IP creation during...
This was last updated ~3 years ago. See [this](https://github.com/kubernetes-sigs/cluster-api-provider-openstack/blob/main/test/e2e/data/cni/calico.yaml).
/kind bug **What steps did you take and what happened:** CAPO users rely on ORC to handle image uploads and reference the ORC Image resource inside OpenStackMachine via spec.image.imageRef. When...
/kind feature **Describe the solution you'd like** Today although the OpenStack cluster supports a multi-availability-zone deployment, the APIServer Load Balancer is only pinned to a single AZ. If this AZ...
**What this PR does / why we need it**: Hosted Control Plane (HCP) clusters do not use a control-plane node in OpenStack, so CAPO should rely on user-specified ports and...
/kind feature ### Context and Background As part of the [initiative to improve status reporting in Cluster API (CAPI) resources](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/proposals/20240916-improve-status-in-CAPI-resources.md), significant changes will be introduced to how resource statuses are...
/kind bug **What steps did you take and what happened:** [A clear and concise description of what the bug is.] I set `volume_api_version: 3` in `clouds.yaml` to use the Cinder...
**What this PR does / why we need it**: Add E2E test to cover region in providerID clusterv1 machine object introduced in issue https://github.com/kubernetes-sigs/cluster-api-provider-openstack/issues/2183 and PR https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/2193 **Special notes for...
/kind feature **Describe the solution you'd like** When creating the loadbalancer in front of the kube-apiserver, it would be useful for us to be able to customise the port the...
/kind feature **Describe the solution you'd like** Right now CAPO allows you to create a trunk from the parent port, by setting `trunk: true` in PortOpts spec. This however is...