Table of Contents generated with DocToc
- v1alpha4 compared to v1alpha5
All users are encouraged to migrate their usage of the CAPO CRDs from older versions to
v1alpha5. This includes yaml files and source code. As CAPO implements automatic conversions between the CRD versions, this migration can happen after installing the new CAPO release.
This only documents backwards incompatible changes. Fields that were added to v1alpha5 are not listed here.
The fields related to the managed API LoadBalancer were moved into a seperate object:
When using Ports it is now possible to specify network and subnet by filter instead of just ID. As a consequence, the relevant ID fields are now moved into the new filter specifications:
- networkId: d-e-a-d
- subnetId: b-e-e-f
Networks are now deprecated. With one exception, all functionality of Networks is now available for Ports. Consequently, Networks will be removed from the API in a future release.
The ability of a Network to add multiple ports with a single directive will not be added to Ports. When moving to Ports, all ports must be added explicitly. Specifically, when evaluating the network or subnet filter of a Network, if there are multiple matches we will add all of these to the server. By contrast we raise an error if the network or subnet filter of a Port does not return exactly one result.
tenantId was previously a synonym for
projectId in both network and subnet filters. This has now been removed. Use
The following fields are removed from network and subnet filters without replacement:
The actual fields were previously already renamed, but we still used the
error prefix in JSON. This was done to align with CAPI, where these fields were renamed in v1alpha3.
errorMessage: Something when wrong
failureMessage: Something when wrong
The following fields were removed without replacement:
rootVolume.sourceUUID has been replaced by using
Image from the OpenStackMachine as appropriate.