v0.4.1

Changes since v0.4.0

⚠️ Breaking Changes

• The IAM policy for the controllers requires a new permission, tag:GetResources. You must manually add this permission to your IAM policy. v0.4.3 adds this to clusterawsadm but it is missing from v0.4.1 and v0.4.2.

✨ New Features

• support for specifying an ENI (#1146)
• Add ability to customize APIServer LB listener port (#1126)
• Record events for credentials and permissions issues (#1129)
• Add prow image building (#1123)
• Specified measurement unit for rootdevicesize comment (#1119)
• Add support for applying custom tags to all AWS resources we manage (#1113)
• Functions for converting v1a1 types to v1a2 (#1081)
• Add AdditionalTags to AWSClusterSpec (#1107)

🐛 Bug Fixes

• a leak of AWS Tags from between Machine and Cluster resources (#1153)
• Specify controller manager broadcaster options so events do not get discarded (#1124)
• use clusterScope's port in APIEndpoint (#1147)
• remove finalizer when machine is absent (#1144)
• Register all available AZs (from public subnets) to the APIServer ELB (#1127)
• handle an unhandled error (#1108)
• fix: use copy builtin correctly for security groups (#1152)

📖 Documentation

• Improve prerequisites document to be embedded in book (#1159)
• Fix broken link in docs/development.md (#1154)
• Fix typo in readme (#1150)
• Update latest AMI information (#1149)
• Fix broken link in docs/README.md (#1125)
• Update getting started guide to prerequisites doc (#1111)

🏃 Others

• Makefile (release) and hack/tools with other repos (#1162)
• E2E test updates (#1122)
• log names are too verbose (#1136)
• Remove release notes from PR template (#1112)
• Context cleanups (#1109)
• Add release binaries target (#1104)
• Add go mod verification in CI (#1131)
• Remove hack/verify-install.sh (#1133)
• Use latest clusterawsadm for generate-example (#1115)

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

Thanks to all our contributors! 😊

v0.3.9

Notable changes

• #1148: Remove use of custom kubeadm cloud-init module

Thanks to everyone who contributed to this release!

Container Image

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

v0.3.8

Notable changes

• Update to cluster-api v0.1.10
• clusterctl now pivots kubeconfig secrets
• #1003: fixed issue where the ELB health check of the apiserver generated a lot of errors that look like http: TLS handshake error from 10.0.1.129:4224: EOF
• #984: guard against missing instanceID when deleting Machines
• #1017: fixed issue where node-labels would grow unbounded if a machine could not be created
• #1010: fixed bug where Service with type=LoadBalancer would fail on workload clusters
• #1002, #1053: made control plane initialization more robust
• #1024: fixed issue where the Go representation of an object was included in the event's text
• #1023: fixed issue where tags were only being applied to private subnets and not public ones
• #1031: added --partition flag to clusterawsadm
• #1063: added --cluster-concurrency and --machine-concurrency flags to the manager to support reconciling more than 1 cluster or machine at a time
• #1089: fixed issue where the manager could wait ~forever for AWS calls, causing it to effectively hang

Thanks to everyone who contributed to this release!

Container Image

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

v0.4.0

🚨 This is a MAJOR release.

This is the first release of cluster-api-provider-aws that works with the v1alpha2 API of Cluster API. Please see the Cluster API Quick Start for how to get up and running quickly with this new release.

The v1alpha2 API of Cluster API has some major breaking changes, which are documented in the proposals listed below.

📖 Proposals

• Machine States & Preboot Bootstrapping
• Cluster Provider Spec and Status as CRDs

⚠️ ProviderSpec fields promoted to New CRDs

• AWSClusterProviderSpec is now AWSCluster
• AWSMachineProviderSpec is now AWSMachine

---

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

v0.3.7

v0.3.7

Breaking Changes (If upgrading from v0.2.x)

• 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.7

Please see the migration document for a detailed list of steps.

Notable changes

• Update cluster-api to v0.1.9
• Query vpc before attempting to delete
• Add backoffs and retries for subsequent AWS calls (#916)
• Cluster actuator: Remove the control plane ready annotation if no control plane machine is ready (#941)

Thanks to everyone who contributed to this release!

Container Image

The manager can be found as this image: us.gcr.io/k8s-artifacts-prod/cluster-api-aws/cluster-api-aws-controller:v0.3.7

v0.3.6

v0.3.6

Breaking Changes (If upgrading from v0.2.x)

• 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.6

Please see the migration document for a detailed list of steps.

Notable changes

• Update cluster-api to v0.1.8
• Add optional pprof http server (#901)
• Update events for Machines (#839)
• Additional Cluster Events (#910)
• Do not update providerID or loadbalancer attachments in Exists (#908)
• Add ownerRef to kubeconfig secret, fix NPE in MachineScope (#926)

Thanks to everyone who contributed to this release!

Container Image

The manager can be found as this image: us.gcr.io/k8s-artifacts-prod/cluster-api-aws/cluster-api-aws-controller:v0.3.6

v0.3.4

v0.3.4

Breaking Changes (If upgrading from v0.2.x)

• 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.4

Please see the migration document for a detailed list of steps.

Notable changes

• Fix controlplane machine race (#779)
• Prefix templated objects with cluster names (#868)
• Avoid infinite APIEndpoints (#881)
• Add additionalUserDataFiles to ClusterSpec (#879)
• Fix ELB panic on deletion (#875)
• Don't rely on status for deleting security group ingress rules (#893)
• Update cluster-api to v0.1.6

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.4

v0.3.3

v0.3.3

Breaking Changes (If upgrading from v0.2.x)

• 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.3

Please see the migration document for a detailed list of steps.

Notable changes

• clusterctl delete broken on v0.3.2 #861

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.3

v0.3.2

v0.3.2

Breaking Changes (If upgrading from v0.2.x)

• 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.2

Please see the migration document for a detailed list of steps.

Notable changes

• Updates cluster-api components to v0.1.4
• UserData size is now logged #853
• Support was added for the cluster-api NodeRef Controller #830

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.2

v0.3.1

Breaking Changes (If upgrading from v0.2.x)

• 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.1

Please see the migration document for a detailed list of steps.

Notable changes

AWSMachineProviderSpec now has a field named availabilityZone that lets you specify an availability zone to create an instance in rather than having to specify a subnet ID.

Updates cluster-api components to v0.1.3

The bigger bug fixes

• Add ModifyVpcAttribute and DescribeVolumes permissions
• Use provided NodeRegistrationOptions as base
• Allow Nodes to talk to Kubelet API Port
• Ignore deleted control plane machines
• Add logic to handle implicit route table associations to main route table

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.1