Today I am pleased to announce the release of the v1alpha2 API version of Cluster API. This has been a huge effort, spanning approximately 5 months of hard work from dozens of contributors. Thank you to everyone who contributed!!!
This is a major release, with breaking changes from the previous API version, v1alpha1.
Highlights of this release include:
- We have separated node bootstrapping (e.g. kubeadm) and machine provisioning, so you can mix and match Kubernetes distributions and infrastructure providers.
- Provider-specific cluster and machine settings now live in proper Custom Resource Definitions (CRDs) and have first-class support for OpenAPI-based validation.
New quick start guide!
We have also added a new quick start guide on how to get from zero to a running cluster using Cluster API.
List of v1alpha2-compatible releases
Below you’ll find links to Cluster API as well as providers that have been updated to support v1alpha2 (additional providers are in the process of being updated).
Cluster API Bootstrap Provider - Kubeadm
Cluster API Provider - AWS
Cluster API Provider - vSphere
Container image - manager:
Container image - manifests:
Cluster API Provider - Docker (for development/testing only)
If you have existing v1alpha1 clusters
If you have existing clusters that you manage with Cluster API v1alpha1, we recommend you continue to use v1alpha1 for them. We are working on tooling to migrate v1alpha1 Clusters and Machines to v1alpha2. Stay tuned for future updates on this effort.
We will be continuing to improve our documentation and flesh out our v1alpha1 to v1alpha2 migration tooling.
We also will be starting our planning for v1alpha3 in the next couple of weeks. If you have features you’d like to see us add, please make sure to file GitHub issues!