Releases: giantswarm/cluster-api-provider-aws-app
Releases · giantswarm/cluster-api-provider-aws-app
v2.27.0
v2.26.0
Added
- Support EC2 lifecycle hooks for machine pools
Changed
- Build: ensure using the correct variant of yq
v2.25.0
Changed
- Bump CAPA version
v2.7.1-gs-*
. This bumps CAPA tov2.7.1
and applies the customizations we already had in our fork.
Fixed
- Filter out AWS internal tags from subnet tags
v2.24.0
Added
- Expose the
maxHealthyPercentage
property to allow setting the maximum percentage of healthy machines in the Auto Scaling Group during upgrades.
v2.23.0
Changed
- Bump CAPA version v2.5.2-gs-11cb106a4. This bumps CAPA to
v2.5.2
and applies the customizations we already had in our fork.
v2.22.0
Changed
- Bump CAPA version v2.4.2-gs-70b4664c1. This bumps CAPA to
v2.4.2
and apply the customizations we already had in our fork.
v2.21.0
Changed
- Reduce sync-period to 2 minutes to improve scale-up taint removal.
v2.20.0
Changed
- Cancel instance refresh on any relevant change to ASG instead of blocking until previous one is finished (which may have led to failing nodes due to outdated join token)
- Try deleting machine pool user data file from S3 when pruning an old launch template version
v2.19.1
Fixed
- Fix for the new feature of writing user data to S3 bucket for
AWSMachinePool
: on cluster deletion, delete machine pool user data files that did not get deleted yet by the S3 bucket lifecycle policy. Otherwise, CAPA would have left the S3 bucket behind on deletion since it was not empty.
v2.19.0
Added
- Support for writing user data to S3 bucket for
AWSMachinePool