Skip to content

Releases: gardener/gardener-extension-provider-aws

v1.8.2

04 Jun 14:54
Compare
Choose a tag to compare

[gardener-extension-provider-aws]

Improvements

  • [OPERATOR] An issue preventing extensionsv1alpha1.BackupEntry to be deleted is now fixed. (e00e7e8)

Docker Images

gardener-extension-provider-aws: eu.gcr.io/gardener-project/gardener/extensions/provider-aws:v1.8.2
gardener-extension-validator-aws: eu.gcr.io/gardener-project/gardener/extensions/validator-aws:v1.8.2

v1.7.2

02 Jun 10:45
Compare
Choose a tag to compare

[gardener-extension-provider-aws]

Improvements

  • [OPERATOR] The cloud-controller-manager is now scrapeable by Prometheus, fixing the false negative CloudControllerManagerDown alert. (#110, @vpnachev)

Docker Images

gardener-extension-provider-aws: eu.gcr.io/gardener-project/gardener/extensions/provider-aws:v1.7.2
gardener-extension-validator-aws: eu.gcr.io/gardener-project/gardener/extensions/validator-aws:v1.7.2

v1.8.1

28 May 04:33
Compare
Choose a tag to compare

[gardener-extension-provider-aws]

Improvements

  • [OPERATOR] An issue preventing error codes to be properly populated in .status.lastError.codes for Infrastructure is now fixed. (618cbbb)

[gardener]

Improvements

Docker Images

gardener-extension-provider-aws: eu.gcr.io/gardener-project/gardener/extensions/provider-aws:v1.8.1
gardener-extension-validator-aws: eu.gcr.io/gardener-project/gardener/extensions/validator-aws:v1.8.1

v1.8.0

26 May 16:43
Compare
Choose a tag to compare

[gardener-extension-provider-aws]

Most notable changes

  • [USER] It is now possible to bring your own, pre-created Elastic IP and let the AWS extension associate it when creating NAT gateways. Please consult this documentation to get more information. (#96, @rfranzke)

Improvements

  • [OPERATOR] ClusterRoles for the machine-controller-manager that might be orphaned now as they created with an earlier, buggy version of this controller are now cleaned up during startup. (#104, @rfranzke)
  • [OPERATOR] The cloud-controller-manager is now scrapeable by Prometheus, fixing the false negative CloudControllerManagerDown alert. (#103, @rfranzke)
  • [OPERATOR] The pre-defined ValidatingWebhookConfiguration assets now set sideEffects=None. This enables dry-run related operations, like kubectl diff, for core.gardener.cloud resources. (#89, @timuthy)

[cloud-provider-aws]

Improvements

[gardener]

Improvements

  • [USER] The generic Worker actuator does now exit its reconciliation flows early if it detects an error during the machine reconciliation. This allows to faster propagate problems to the end-user. (gardener/gardener#2348, @rfranzke)
  • [USER] The extension health check library does now allow individual health checks to return the Progressing status. This allows to provide more accurate status information and less false negative health reports. (gardener/gardener#2289, @rfranzke)
  • [OPERATOR] The Gardenlet sets an additional annotation to Extension CRDs during reconciliation to guarantee an update event for the watching clients. (gardener/gardener#2290, @danielfoehrKn)
  • [OPERATOR] Fixes a bug in the extension libraries that could lead to duplicate reconciliation of extension resources. When respecting the operation annotation set by the Gardenlet during reconciliation, extension controllers now only watch the Extension CRD. (gardener/gardener#2290, @danielfoehrKn)
  • [OPERATOR] Fixes a bug in the extension library of all extension resources that lead to not stopping the reconciliation of extension resources when the Shoot is in 'failed' state (Shoot.Status.lastOperation.state = Failed). (gardener/gardener#2279, @danielfoehrKn)
  • [OPERATOR] Fixed a bug in the health check library that leads to too many health checks being executed when the Extension.Status changes. (gardener/gardener#2307, @danielfoehrKn)
  • [OPERATOR] Fixed the health check condition.lastTransitionTime in the health check library. (gardener/gardener#2307, @danielfoehrKn)

[machine-controller-manager]

Improvements

Docker Images

gardener-extension-provider-aws: eu.gcr.io/gardener-project/gardener/extensions/provider-aws:v1.8.0
gardener-extension-validator-aws: eu.gcr.io/gardener-project/gardener/extensions/validator-aws:v1.8.0

v1.7.1

12 May 11:11
Compare
Choose a tag to compare

[gardener]

Improvements

Docker Images

gardener-extension-provider-aws: eu.gcr.io/gardener-project/gardener/extensions/provider-aws:v1.7.1
gardener-extension-validator-aws: eu.gcr.io/gardener-project/gardener/extensions/validator-aws:v1.7.1

v1.7.0

07 May 06:54
Compare
Choose a tag to compare

[gardener-extension-provider-aws]

Improvements

  • [USER] A bug during the CSI migration has been fixed that may cause the CSIMigration<Provider>Complete feature gate to be set to early. (#73, @rfranzke)
  • [USER] When worker pools with the io1 volume type are used then the validation does now enforce that the .spec.provider.workers[].providerConfig does contain a proper AWS WorkerConfig (that states the iops). (#72, @rfranzke)
  • [USER] Documentation how to use WorkerConfig (e.g., to set the iops for io1 volumes) has been added to https://github.com/gardener/gardener-extension-provider-aws/blob/master/docs/usage-as-end-user.md. (#71, @rfranzke)
  • [OPERATOR] WorkerPool labels will be added to AWS EC2 as the VM tag (#87, @sdojjy)
  • [OPERATOR] Fixed a bug in the healthcheck library that prevents checks after a Shoot has been woken up from hibernation. Gardener extensions require a minor change during the healthcheck registration. (#86, @ialidzhikov)
  • [OPERATOR] kubernetes-csi/external-snapshotter components are updated to v2.1.1. (#82, @ialidzhikov)
  • [OPERATOR] Golang version is updated to 1.14.2. (#79, @ialidzhikov)
  • [OPERATOR] gardener-extension-provider-aws now deploys required CSI snapshot controller and in this way fixes the issue with VolumeSnapshot resources which are not getting ready to use. (#76, @ialidzhikov)
  • [OPERATOR] An issue preventing csi-driver-controller container to start because of too low memory recommendation by VPA is now fixed. (#70, @ialidzhikov)
  • [OPERATOR] implement Migrate and Restore functionality (#62, @vlvasilev)

[gardener]

Improvements

Docker Images

gardener-extension-provider-aws: eu.gcr.io/gardener-project/gardener/extensions/provider-aws:v1.7.0
gardener-extension-validator-aws: eu.gcr.io/gardener-project/gardener/extensions/validator-aws:v1.7.0

v1.6.2

24 Apr 12:14
Compare
Choose a tag to compare

[gardener-extension-provider-aws]

Improvements

Docker Images

gardener-extension-provider-aws: eu.gcr.io/gardener-project/gardener/extensions/provider-aws:v1.6.2
gardener-extension-validator-aws: eu.gcr.io/gardener-project/gardener/extensions/validator-aws:v1.6.2

v1.6.1

17 Apr 07:20
Compare
Choose a tag to compare

[gardener-extension-provider-aws]

Improvements

  • [OPERATOR] An issue preventing csi-driver-controller container to start because of too low memory recommendation by VPA is now fixed. (2a95f67)

Docker Images

gardener-extension-provider-aws: eu.gcr.io/gardener-project/gardener/extensions/provider-aws:v1.6.1
gardener-extension-validator-aws: eu.gcr.io/gardener-project/gardener/extensions/validator-aws:v1.6.1

v1.6.0

16 Apr 15:24
Compare
Choose a tag to compare

[gardener-extension-provider-aws]

Action Required

  • [USER] The AWS extension does now support shoot clusters with Kubernetes version 1.18. You should consider the Kubernetes release notes before upgrading to 1.18. Please note that the AWS EBS CSI driver will be used for 1.18 shoots. It is compatible with the legacy volume provisioners, however, you might want to update your storage classes and volume handling accordingly. Please find more information about CSI in the official Kubernetes documentation. (#64, @rfranzke)

Improvements

  • [OPERATOR] kube-controller-manageer no longer has access to blocked CIDRs. (#69, @mvladev)
  • [OPERATOR] g/gardener-extensions does now require the g/terraformer@v1.0.0. (#57, @ialidzhikov)

[cloud-provider-aws]

Improvements

[gardener-extensions]

Improvements

[terraformer]

Action Required

  • [OPERATOR] The Terraformer does now lookup the relevant data stored in ConfigMaps or Secrets live from the system instead of relying on mounted volumes. This is a breaking change as the volume mount approach does no longer work, please adapt your manifests according to the examples. The rationale behind it is to not rely on potentially stale kubelet cache while it mounts the volume which may, in rare cases, cause state loss. (gardener/terraformer#37, @rfranzke)

Improvements

  • [OPERATOR] nsxt and random providers are now removed from the terraform bundle. (gardener/terraformer#38, @ialidzhikov)
  • [OPERATOR] terraformer does no longer ignore the termination signals sent to PID 1. It does now send a termination signal to the terraform process itself and waits for its completion. This should prevent rare cases in which the terraformer was not storing the state of created infrastructure resources. (gardener/terraformer#36, @ialidzhikov)

Docker Images

gardener-extension-provider-aws: eu.gcr.io/gardener-project/gardener/extensions/provider-aws:v1.6.0
gardener-extension-validator-aws: eu.gcr.io/gardener-project/gardener/extensions/validator-aws:v1.6.0

v1.5.0

02 Apr 05:43
Compare
Choose a tag to compare

[gardener-extension-provider-aws]

Action Required

  • [OPERATOR] ⚠️ This version is not compatible with Gardener < v1.2. (#42, @georgekuruvillak)
    • The controlplanebackup webhook is removed as of gardener/gardener#1762. The controlplaneexposure webhook that was previously targeting StatefulSets is now targeting Etcd resources of the druid.

Most notable changes

  • [DEVELOPER] A new integration test for infrastructure reconciliation and deletion has been added. (#54, @rfranzke)

Improvements

  • [USER] The VPC gateway endpoints provided in the infrastructure configuration are now correctly provisioned. (#54, @rfranzke)
  • [USER] The Infrastructure deletion does now succeed in case it never created anything but the cloud provider secret does not contain the correct credentials. (#44, @rfranzke)
  • [USER] The Worker deletion does now succeed in case the cloud provider credentials were changed. (#44, @rfranzke)
  • [USER] Do not mutate kube-apiserver exposure resources which Gardener marks as managed by it with core.gardener.cloud/apiserver-exposure: gardener-managed label. (#37, @mvladev)
  • [OPERATOR] The AWS provider now allows Gardener to restart the Cloud-Controller-Manager and the Machine-Controller-Manager (see gardener/gardener#2098 for more information). (#65, @timuthy)
  • [OPERATOR] The eth0 interface name is no longer hard-coded, instead the non-virtual network interface names are now dynamically detected. (#50, @vpnachev)
  • [OPERATOR] The infrastructure controller does no longer release the finalizer of Infrastructure CR if it cannot find a given output variables. This allows terraform destroy to be invoked even when there is no output variables in the terraform.tfstate. (#49, @ialidzhikov)
  • [OPERATOR] Now it is possible to modify the gateway endpoints list networks.vpc.gatewayEndpoints after the shoot is created. (#41, @tareqhs)
  • [DEVELOPER] Fix nil pointer when applying machine class chart (#46, @mvladev)

[cloud-provider-aws]

Improvements

[gardener-extensions]

Improvements

[machine-controller-manager]

Most notable changes

Improvements

[terraformer]

Improvements

Docker Images

gardener-extension-provider-aws: eu.gcr.io/gardener-project/gardener/extensions/provider-aws:v1.5.0
gardener-extension-validator-aws: eu.gcr.io/gardener-project/gardener/extensions/validator-aws:v1.5.0