Releases: kubernetes-sigs/cluster-api-provider-aws
v0.3.8
Notable changes
- Update to cluster-api v0.1.10
clusterctlnow 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
⚠️ ProviderSpec fields promoted to New CRDs
AWSClusterProviderSpecis nowAWSClusterAWSMachineProviderSpecis nowAWSMachine
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
Cloud provider integration and general hardening
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
Multi control plane clusters and more reliable creation
Multi-node control plane clusters
It is now easy to get a multi-node control plane cluster. This release ships with an example that will create a 3-node control plane cluster with 1 worker node in a single availability zone. This is a small step towards cluster-api-provider-aws supporting highly availble clusters with minimal configuration. It is possible to create a highly available cluster, but much of the leg work is manual. Please see documentation for more information on how to create highly available clusters
Reliabilty
Previous releases had some issues with clusters getting stuck while being created. That was due to over-eagerness in reconciling the infrastrucutre. The code now only reconciles things when something has changed.
A good number of nil derefence errors have been cleaned up so you should be seeing fewer stack traces in your logs.
Supported Kubernetes versions
This release adds support for a few more Kubernetes versions including v1.14.0 and v1.14.1. You can find a complete list here.
Custom AMIs
Support has been added for custom AWS organizational IDs which allows you to upload your own AMIs to your own organization and use those to launch instances from.
Root device size customization
A configuration option for an AWS image's root device size has been added.