v1.15.2

[gardener]

Most notable changes

• [OPERATOR] Machines without .spec.providerID or .status.node will no longer be persisted in the Worker' .status.state field. This is to prevent unnecessary updates to the ShootState resources. (gardener/gardener#2909, @rfranzke)

Docker Images

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

v1.15.1

[gardener-extension-provider-aws]

Most notable changes

• [USER] The deletion of VMs referring to a non-existing disk image fails currently. This MCM version hotfix fixes this issue. (#186, @prashanth26)

Docker Images

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

v1.15.0

[gardener-extension-provider-aws]

Most notable changes

• [USER] The volumeBindingMode of the StorageClasses managed by Gardener is now switched to WaitForFirstConsumer. (#179, @ialidzhikov)
• [USER] The AWS extension does now support shoot clusters with Kubernetes version 1.19. You should consider the Kubernetes release notes before upgrading to 1.19. (#176, @rfranzke)

Improvements

• [OPERATOR] KCM mounts /usr/share/ca-certificates required for certain OS (e.g CoreOS 2512.3.0), (#173, @danielfoehrKn)

[cloud-provider-aws]

Improvements

• [OPERATOR] k8s.io/legacy-cloud-providers is now updated to v1.19.0. (gardener/cloud-provider-aws@d19de317aeafad671a0cc7b0e255bb9b8d04ac5be)
• [DEVELOPER] The alpine version has been updated to v3.12.0. (gardener-attic/cloud-provider-aws@6f75cd7)
• [DEVELOPER] The Golang version has been updated to v1.15.0. (gardener-attic/cloud-provider-aws@6f75cd7)

[terraformer]

Improvements

• [OPERATOR] terraform-provider-alicloud is now updated to 1.94.0. (gardener/terraformer#45, @minchaow)

Docker Images

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

v1.14.1

[gardener-extension-provider-aws]

Improvements

• [OPERATOR] KCM mounts /usr/share/ca-certificates required for certain OS (e.g CoreOS 2512.3.0), (845fc94)

Docker Images

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

v1.13.1

[gardener-extension-provider-aws]

Improvements

• [OPERATOR] KCM mounts /usr/share/ca-certificates required for certain OS (e.g CoreOS 2512.3.0), (20a2941)

v1.14.0

[gardener-extension-provider-aws]

Improvements

• [OPERATOR] The StorageClasses in the shoot cluster managed by Gardener are now re-created in case the update request failed due to changed immutable fields. (#168, @vpnachev)

[gardener]

Improvements

• [OPERATOR] The generic worker actuator now also reports failed machines from the corresponding machine deployment in case the shoot cluster is being hibernated. Earlier scale down issues during hibernation were not reported to users, e.g. if something was wrong with the configured cloud provider account and thus the machine deletion was denied. (gardener/gardener#2759, @timuthy)
• [OPERATOR] Kubernetes dependencies are now updated to v0.17.11. (gardener/gardener#2728, @ialidzhikov)
• [OPERATOR] The error code mapping has been extended to categorize certain common issues upfront and furnish them with error codes. (gardener/gardener#2702, @rfranzke)

Docker Images

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

v1.13.0

[gardener-extension-provider-aws]

Action Required

• [USER] The Infrastructure controller does now check for the required VPC attributes enableDnsSupport and enableDnsHostnames to be enabled when an existing VPC is used for the shoot infrastructure. If any of them is disabled then the reconciliation will fail (see also user guide). Make sure to enable these attributes for your existing VPCs that are used for shoots. (#161, @rfranzke)

Improvements

• [USER] A bug has been fixed which prevented the .networks.zones[].elasticIPAllocationID field in the InfrastructureConfig from being changed. (#165, @rfranzke)
• [USER] amazon/aws-ebs-csi-driver is now updated to v0.6.0. (#163, @ialidzhikov)
• [OPERATOR] provider-aws does now allow configuring the --volume-attach-limit flag of the AWS EBS CSI driver via aws.provider.extensions.gardener.cloud/volume-attach-limit annotation on Shoot. (#164, @ialidzhikov)
• [OPERATOR] A PodDisruptionBudget for the validation server is now automatically deployed as part of its Helm chart if the replica count is larger than 1. (#162, @rfranzke)
• [OPERATOR] Gateway endpoints are now also created when existing vpc (networks.vpc.id) is used. (#160, @ialidzhikov)

Docker Images

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

v1.12.0

[gardener-extension-provider-aws]

Action Required

• [OPERATOR] For EC2 instance types that do not support EBS encrypted volumes, please set the worker pool EBS volume encryption flag to false as mentioned in the machine volume settings. (#147, @prashanth26)

Most notable changes

• [USER] Enable encryption by default for AWS instance EBS volumes. (#147, @prashanth26)
• [OPERATOR] The logging configuration has been adapted to cater with Loki which was introduced as part of gardener/gardener#2515. If an older version of this extension is used with a Gardener version >= v1.8 and the Logging feature gate is enabled then the fluent-bit matcher won't catch the log anymore (resulting in the logs being collected, but not nicely parsed and instead displayed in nested JSON). It is recommended update to at least this extension version when Gardener >= v1.8 is used and the Logging feature gate is enabled. (#133, @Kristian-ZH)

Improvements

• [USER] create default VolumeSnapshotClass if kubernetes version >= 1.18 (#146, @runzexia)
• [USER] StorageClasses now allow for expansion of PVCs. (#141, @mvladev)
• [OPERATOR] The default webhook server port is now changed to 10250. (#153, @stoyanr)
• [OPERATOR] Worker extension allows configuring following parameters on machine-deployment: drainTimeout, creationTimeout, healthTimeout, maxEvictRetries, nodeConditions. (#149, @hardikdr)

[cloud-provider-aws]

Improvements

• [OPERATOR] k8s.io/legacy-cloud-providers is now updated to v0.17.9. (gardener-attic/cloud-provider-aws#4, @ialidzhikov)
• [OPERATOR] k8s.io/legacy-cloud-providers is now updated to v0.18.6. (gardener-attic/cloud-provider-aws#5, @ialidzhikov)

[machine-controller-manager]

Improvements

• [OPERATOR] Avoids race between secret finalizer creation/deletion between in-tree & OOT controllers (gardener/machine-controller-manager#487, @prashanth26)
• [OPERATOR] Enable finer machine configurations per MachineDeployment/MachineSet/Machines basis. Exposed configurations: MachineDrainTimeout, MachinHealthTimeout, MachineCreationTimeout, MaxEvictRetries, NodeConditions. (gardener/machine-controller-manager#478, @hardikdr)
• [DEVELOPER] Increased default concurrent worker syncs from 5 --> 10 (gardener/machine-controller-manager#491, @prashanth26)

Docker Images

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

v1.11.0

[gardener-extension-provider-aws]

Action Required

• [OPERATOR] Upgrade gardenctl to the latest version as creation of bastion nodes would not succeed. See gardenctl issue for more details. (#139, @mvladev)

Most notable changes

• [OPERATOR] IAM roles, policies and instance profiles for bastion instances are no longer created and existing ones are removed during the next infra reconciliation. (#139, @mvladev)

Improvements

• [USER] The csi-node-driver is now auto-scaled by the VPA in case the Shoot sets .spec.kubernetes.verticalPodAutoscaler.enabled=true. (#129, @rfranzke)
• [OPERATOR] A bug has been fixed, that caused the Infrastructure deletion to be blocked forever in case there are already running terraformer Pods. (#132, @tim-ebert)

[machine-controller-manager]

Improvements

• [OPERATOR] Added an option to use configDrive in the OpenStackMachineClass (gardener/machine-controller-manager#457, @zuzzas)
• [DEVELOPER] Bugfix: Drain machines with only a valid node (name) (gardener/machine-controller-manager#480, @prashanth26)

[terraformer]

Improvements

• [OPERATOR] terraform-provider-aws is now updated to 2.68.0. (gardener/terraformer#42, @ialidzhikov)
• [OPERATOR] terraform-provider-google and terraform-provider-google-beta are now updated to 3.27.0. (gardener/terraformer#42, @ialidzhikov)

Docker Images

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

v1.10.1

[gardener-extension-provider-aws]

Improvements

• [OPERATOR] A bug has been fixed, that caused the Infrastructure deletion to be blocked forever in case there are already running terraformer Pods. (2292163)

Docker Images

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