v0.2.4

Changes since v0.2.3

⚠️ Action Required

The default leader election ID has been updated in this release. When upgrading from a previous v0.2.3 (or older) release you will need to:

1. Scale down the old controllers: kubectl -n capi-system scale deployment/controller-manager --replicas=0.
2. Deploy the updated manifests with the newer image.
3. Scale up the new controllers: kubectl -n capi-system scale deployment/controller-manager --replicas=1.

Failure to scale down the Deployment prior to updating to this version will result in multiple controllers running concurrently during the roll out of the updated controller-manager image.

🐛 Bug Fixes

• Support running alongside other Cluster API pods in the same namespace with leader election enabled (#1492)
• Do not re-queue forever if only cluster is deployed (#1466)
• Update Machine Status with Error Reason and Error Message if infra object is deleted (#1458)
• DeepCopy unstructured object in patch helper Patch method (#1467)
• DeepCopy unstructured objects in helper before patching (#1464)
• Reference to PULL_BASE_REF for image building (#1457)
• Add well-known tolerations to released CAPI manager (#1487)

📖 Documentation

• Fix link in Cluster controller doc (#1479)
• Embed AWS pre-requisites document (#1472)
• Create documentation for machine contracts between components (#1391)
• Broken links to api-conventions doc (#1462)

🏃 Others

• Add common utilities for provider-based testing (#1474)
• unused function isScalingEvent (#1463)
• NodeOutOfDisk condition obsolete in Kubernetes 1.16 (#1476)

The image for this release is: us.gcr.io/k8s-artifacts-prod/cluster-api/cluster-api-controller:v0.2.4

Thanks to all our contributors! 😊