Cluster API provider renaming
Renaming of Cluster API provider
Backwards compatibility for v1alpha3
There is no backwards compatibility between v1alpha3 and v1alpha2 releases of the Cluster API provider for Metal3.
For the v1alpha3 release of Cluster API, the Metal3 provider was renamed from
cluster-api-provider-metal3. The Custom
Resource Definitions were also modified. This post dives into the changes.
From v1alpha3 onwards, the Cluster API provider will be developed in cluster-api-provider-metal3. The v1alpha1 and v1alpha2 content will remain in cluster-api-provider-baremetal. This repository will be archived, but kept for the integration in metal3-dev-env.
Custom Resource Definition modifications
The kind of the Custom Resource Definition (CRD) has been modified for the following objects:
The custom resources deployed need to be modified accordingly.
The prefix of all deployed components for the Metal3 provider was modified
capm3-. The namespace in which the components are deployed by
default was modified from