Skip to content

Releases: gardener/gardener-extension-provider-aws

v1.40.2

23 Nov 16:28
Compare
Choose a tag to compare

[machine-controller-manager-provider-aws]

🏃 Others

v1.40.1

23 Nov 14:24
Compare
Choose a tag to compare

[gardener-extension-provider-aws]

🐛 Bug Fixes

  • [OPERATOR] Remove clusterrole label from aws-custom-route-controller as it prevents reconciliation on existing custom-route-controller deployments. (gardener/gardener-extension-provider-aws#653, @kon-angelo)
    • Remove clusterrole and clusterrolebinding for custom-route-controller in seed-controlplane charts as they are not needed.

v1.40.0

22 Nov 15:59
Compare
Choose a tag to compare

[gardener-extension-provider-aws]

🏃 Others

v1.39.1

26 Oct 12:17
Compare
Choose a tag to compare

v1.39.0

19 Oct 06:44
Compare
Choose a tag to compare

[gardener-extension-provider-aws]

✨ New Features

🐛 Bug Fixes

🏃 Others

[machine-controller-manager-provider-aws]

🏃 Others

v1.38.2

28 Sep 09:51
Compare
Choose a tag to compare

[gardener-extension-provider-aws]

🐛 Bug Fixes

v1.38.1

19 Sep 15:19
Compare
Choose a tag to compare

[gardener-extension-provider-aws]

🏃 Others

v1.38.0

15 Sep 10:41
Compare
Choose a tag to compare

[gardener-extension-provider-aws]

⚠️ Breaking Changes

✨ New Features

🏃 Others

[aws-custom-route-controller]

🐛 Bug Fixes

[machine-controller-manager]

✨ New Features

🐛 Bug Fixes

🏃 Others

[machine-controller-manager-provider-aws]

✨ New Features

  • [USER] Throughput is now configurable for volume types. Its validation i.e. whether it is allowed or not for the particular volume type and is within the range, is done on the provider(AWS) side. Currently only gp3 volume have configurable throughput. (gardener/machine-controller-manager-provider-aws#95, @rishabh-11)

[terraformer]

🏃 Others

v1.37.0

02 Aug 12:12
Compare
Choose a tag to compare

[gardener-extension-provider-aws]

⚠️ Breaking Changes

✨ New Features

🐛 Bug Fixes

  • [USER] Users can now set IOPS for a GP3 volume type. Validation of IOPS (i.e. whether it is allowed and is in the specified range for a volume type) is done on the AWS side, so feedback will arrive once the volume is created. (gardener/gardener-extension-provider-aws#561, @rishabh-11)
  • [OPERATOR] provider-aws now mutates the cluster-autoscaler Deployment by implementing the EnsureClusterAutoscalerDeployment function. This is required in the context of kubernetes/autoscaler#4517 - cluster-autoscaler supports --feature-gates flag and provider extensions have to mutate the cluster-autoscaler Deployment to add the CSI related feature gates to it. (gardener/gardener-extension-provider-aws#562, @ialidzhikov)

🏃 Others

[aws-lb-readvertiser]

🏃 Others

[machine-controller-manager]

⚠️ Breaking Changes

  • [OPERATOR] The default leader election resource lock of machine-controller-manager has been changed from endpointsleases to leases. (gardener/machine-controller-manager#711, @acumino)
    • Please make sure, that you had at least [email protected] running before upgrading to v0.46.0, so that it has successfully acquired leadership with the hybrid resource lock (endpointsleases) at least once.

🐛 Bug Fixes

🏃 Others

[machine-controller-manager-provider-aws]

🏃 Others

[terraformer]

🏃 Others

v1.36.0

07 Jun 13:13
Compare
Choose a tag to compare

[gardener-extension-provider-aws]

⚠️ Breaking Changes

✨ New Features

🐛 Bug Fixes

  • [OPERATOR] An issue causing admission-aws to fail a Shoot creation request with .spec.provider.infrastructureConfig=nil with 500 Internal server error is now fixed. admission-aws now properly indicates in the response that the corresponding field is required. (gardener/gardener-extension-provider-aws#549, @ialidzhikov)

📖 Documentation

🏃 Others

[aws-lb-readvertiser]

🏃 Others

[cloud-provider-aws]

✨ New Features

🏃 Others

[machine-controller-manager]

📖 Documentation

🏃 Others

[machine-controller-manager-provider-aws]

📰 Noteworthy

[terraformer]

🏃 Others