Supported release versions

The Cluster API Provider Metal3 (CAPM3) team maintains the two most recent minor releases; older minor releases are immediately unsupported when a new major/minor release is available. Test coverage will be maintained for all supported minor releases and for one additional release for the current API version in case we have to do an emergency patch release. For example, if v1.5 and v1.6 are currently supported, we will also maintain test coverage for v1.4 for one additional release cycle. When v1.7 is released, tests for v1.4 will be removed.

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:

Cluster API Provider Metal3

Minor releaseAPI versionStatus
v1.6v1beta1Supported
v1.5v1beta1Supported
v1.4v1beta1Tested
v1.3v1beta1EOL
v1.2v1beta1EOL
v1.1v1beta1EOL

IP Address Manager

Minor releaseAPI versionStatus
v1.6v1beta1Supported
v1.5v1beta1Supported
v1.4v1beta1Tested
v1.3v1beta1EOL
v1.2v1alpha1EOL
v1.1v1alpha1EOL

The compatability of IPAM and CAPM3 API versions with CAPI is discussed here.

Baremetal Operator

Since capm3-v1.1.2, BMO follows the semantic versioning scheme for its own release cycle, the same way as CAPM3 and IPAM. Currently, we have release-0.5, release-0.4 and release-0.3 release branches for v0.5.x v0.4.x and v0.3.x release cycle respectively and as such two braches are maintained as supported releases. Following table summarizes BMO release/test process:

Minor releaseStatus
v0.5Supported
v0.4Supported
v0.3Tested
v0.2EOL
v0.1EOL

Image tags

The Metal³ team provides container images for all the main projects and also many auxilary tools needed for tests or otherwise useful. Some of these images are tagged in a way that makes it easy to identify what version of Cluster API provider Metal³ they are tested with. For example, we tag MariaDB container images with tags like capm3-v1.6.0, where v1.6.0 would be the CAPM3 release it was tested with.

All container images are published through the Metal³ organization in Quay. Here are some examples:

  • quay.io/metal3-io/cluster-api-provider-metal3:v1.6.0
  • quay.io/metal3-io/baremetal-operator:v0.5.0
  • quay.io/metal3-io/ip-address-manager:v1.6.0
  • quay.io/metal3-io/ironic:v23.1.0
  • quay.io/metal3-io/mariadb:capm3-v1.6.0

CI Test Matrix

The table describes which branches/image-tags are tested in each periodic CI tests:

INTEGRATION TESTSCAPM3 branchIPAM branchBMO branch/tagKeepalived tagMariaDB tagIronic tag
daily_main_integration_test_ubuntu/centosmainmainmainlatestlatestlatest
daily_main_e2e_integration_test_ubuntu/centosmainmainmainlatestlatestlatest
daily_release-1-6_integration_test_ubuntu/centosrelease-1.6release-1.6release-0.5v0.5.0latestlatest
daily_release-1-5_integration_test_ubuntu/centosrelease-1.5release-1.5release-0.4v0.4.0latestlatest
daily_release-1-4_integration_test_ubuntu/centosrelease-1.4release-1.4release-0.3v0.3.1latestlatest
FEATURE AND E2E TESTSCAPM3 branchIPAM branchBMO branch/tagKeepalived tagMariaDB tagIronic tag
daily_main_e2e_feature_test_ubuntu/centosmainmainmainlatestlatestlatest
daily_release-1-6_e2e_feature_test_ubuntu/centosrelease-1.6release-1.6release-0.5v0.5.0latestlatest
daily_release-1-5_e2e_feature_test_ubuntu/centosrelease-1.5release-1.5release-0.4v0.4.0latestlatest
daily_release-1-4_e2e_feature_test_ubuntu/centosrelease-1.4release-1.4release-0.3v0.3.1latestlatest
daily_main_feature_tests_ubuntu/centosmainmainmainlatestlatestlatest
EPHEMERAL TESTSCAPM3 branchIPAM branchBMO branch/tagKeepalived tagMariaDB tagIronic tag
daily_main_e2e_ephemeral_test_centosmainmainmainlatestlatestlatest

All tests use latest images of VBMC and sushy-tools.