Breaking Changes
- Labels for Cluster API managed infrastructure and cloud-provider managed infrastructure overlapped. The breaking change introduces a new label for Cluster API to use as well as a tool to convert labels on existing clusters to the new format.
Action to migrate an existing v0.2 CAPA management cluster to v0.3.0
Please see the migration document for a detailed list of steps.
Notable changes
This release allows the out-of-tree kubernetes cloud-provider to manage resources it normally manages while keeping Cluster API managed assets tagged as such.
Cluster API owned resources are tagged with sigs.k8s.io/cluster-api-provider-aws/managed: true
cloud-provider owned resources are tagged with kubernetes.io/cluster/<cluster-name>: owned
The bigger bug fixes
- Now works with existing subnets and security groups.
- Removes a race condition around multiple control planes joining a cluster simultaneously.
- Fixes an issue where AWS would hang forever.
- Taints get copied from MachineDeployment into Machines via Kubeadm
Thanks to everyone who contributed to this release!
Container Image
The manager can be found as this image: gcr.io/cluster-api-provider-aws/cluster-api-aws-controller:v0.3.0