Supported release versions
The Cluster API Provider Metal3 (CAPM3) team maintains the following branches for CAPM3 for different API versions.
- CAPM3
- main
- v1beta1
- release-1.2
- v1beta1
- release-1.1
- v1beta1
- main
Currently, in Metal³ organization only CAPM3 and IPAM follow CAPI release cycles. The supported versions (excluding release candidates) for CAPM3 and IPAM releases are as follows:
- CAPM3
- v1beta1
- v1.2.0, v1.1.3, v1.1.2, v1.1.1, v1.1.0
- v1alpha5
- v0.5.5, v0.5.4, v0.5.3, v0.5.2, v0.5.1, v0.5.0
- v1beta1
- IPAM
- v1alpha1
- v1.2.0, v1.1.4, v1.1.3, v1.1.2, v1.1.1, v1.1.0, v0.1.2, v0.1.1, v0.1.0
- v1alpha1
The compatability of IPAM and CAPM3 API versions with CAPI is discussed here.
Since BMO and Ironic do not follow similar release cycles they are backward compatible. However, we used to tag the BMO and Ironic code base whenever we do a release in CAPM3 prior to CAPM3 release v1.1.3
. The tags used to have a prefix capm3- and the suffix was always the corresponding capm3- release version. So for example, if we cut a v1.0.0
release for CAPM3 we created a tag in the BMO and Ironic code base with capm3-v1.0.0
. Please note, currently that is applicable only for Ironic starting from CAPM3 release v1.1.3
and onwards.
Following the same trend, the following tags for BMO and Ironic are available and supported (image tags):
- capm3-v1.2.0 (Ironic Only)
- capm3-v1.1.3 (Ironic only)
- capm3-v1.1.2 (BMO and Ironic)
- capm3-v1.1.1
- capm3-v1.1.0
- capm3-v0.5.5
- capm3-v0.5.4
- capm3-v0.5.3
- capm3-v0.5.2
- capm3-v0.5.1
- capm3-v0.5.0
Up until capm3-v1.1.2
tag, BMO follows the same trend as Ironic. However, since capm3-v1.1.2
, BMO follows the semantic versioning scheme for its own release cycle, the same way as CAPM3 and IPAM. At the moment, we always cut rolling releases from the main branch of BMO and tag them with the release version (i.e: v0.1.X). Here are available and supported BMO image tags:
- v0.1.1
- v0.1.0
Supported Image tags
Supported container images for BMO and Ironic can be found in quay. Examples are:
- quay.io/metal3-io/ironic:capm3-v1.2.0
- quay.io/metal3-io/baremetal-operator:v0.1.1
Supported container images for CAPM3 and IPAM will always follow the supported release version tags and can be found in quay. Examples are:
- quay.io/metal3-io/cluster-api-provider-metal3:v1.2.0
- quay.io/metal3-io/ip-address-manager:v1.2.0