v1.14.0

[gardener-extension-provider-azure]

Improvements

• [OPERATOR] github.com/gardener/gardener dependency is now updated to v1.11.1. (#175, @dkistner)
• [OPERATOR] The following options can now be configured through the extension's Helm chart values charts/gardener-extension-provider-azure/values.yaml: (#173, @timuthy)
  • Health check worker count
  • minAllowed values for VPA
• [OPERATOR] Add common certificate directory mounts to the CCM. (#167, @danielfoehrKn)
• [OPERATOR] kubernetes-sigs/azuredisk-csi-driver is now updated to v0.9.0. (#165, @ialidzhikov)
• [OPERATOR] The Webhook ensurer does not remove or add the /etc/ssl directory for kube apiserver deployments any more. This is done by the Gardenlet for version >= 1.10.0. (#164, @danielfoehrKn)

[cloud-provider-azure]

Improvements

• [OPERATOR] k8s.io/legacy-cloud-providers is now updated to v0.17.13. (gardener-attic/cloud-provider-azure@9e40e1f)
• [OPERATOR] k8s.io/legacy-cloud-providers is now updated to v0.18.10. (gardener-attic/cloud-provider-azure@e983941)
• [OPERATOR] k8s.io/legacy-cloud-providers is now updated to v0.19.3. (gardener-attic/cloud-provider-azure@4d96697)

[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)

[machine-controller-manager]

Most notable changes

• [USER] Support for Spot Instances is available in AWS driver. If the spotPrice is empty, price is automatically set to the on-demand price so that Spot instance can launch immediately. (gardener/machine-controller-manager#481, @zuzzas)
• [OPERATOR] Introduced a backoff in re-enqueuing machines on creation/deletion failures. Avoids throttling APIServer & provider calls. (gardener/machine-controller-manager#523, @hardikdr)
• [OPERATOR] RBAC policies have to be updated to allow updating of node/status resources. (gardener/machine-controller-manager#492, @guydaichs)
• [OPERATOR] New flag delete-migrated-machine-class is introduced. When set to true (defaulted to false), deletes any provider-specific machine class (e.g. AWSMachineClass) that has the machine.sapcloud.io/migrated annotation set on it. (gardener/machine-controller-manager#484, @prashanth26)
• [DEVELOPER] Added migration logic for moving from provider-specific machine class to generic machine classes in out of tree code path. On migration, the machine.sapcloud.io/migrated annotation set on the old machine class. (gardener/machine-controller-manager#484, @prashanth26)
• [DEVELOPER] The machine controller adds finalizer only when machine reference is present, deletes it otherwise. (gardener/machine-controller-manager#484, @prashanth26)

Improvements

• [USER] Retry when secret is referred by machineClass is missing (gardener/machine-controller-manager#495, @AxiomSamarth)
• [USER] Node condition is added to the status of terminating nodes indicating the termination start time and reason (Unhealthy|ScaleDown) (gardener/machine-controller-manager#492, @guydaichs)
• [OPERATOR] Added a more comprehensive set of events to trigger machine class reconciliations. (gardener/machine-controller-manager#532, @prashanth26)
• [OPERATOR] Finalizers are added by default for all machine class objects. (gardener/machine-controller-manager#532, @prashanth26)
• [OPERATOR] AWS: Allow deletion of VMs even on list image or modify instance failure (gardener/machine-controller-manager#516, @prashanth26)
• [OPERATOR] All nodes under machine deployments being rolled-out are annotated with cluster-autoscaler.kubernetes.io/scale-down-disabled: "True" during the period of rolling-update. (gardener/machine-controller-manager#496, @hardikdr)
• [OPERATOR] A new command line flag autoscaler-scaldown-annotation-during-rollout is introduced to disable annotating the nodes with cluster-autoscaler annotation cluster-autoscaler.kubernetes.io/scale-down-disabled during rollout. (gardener/machine-controller-manager#496, @hardikdr)
• [DEVELOPER] Adds a new phase CrashLoopBackOff that is set due to machine creation failures. (gardener/machine-controller-manager#523, @hardikdr)

Docker Images

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

v1.13.1

[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-azure: eu.gcr.io/gardener-project/gardener/extensions/provider-azure:v1.13.1
gardener-extension-validator-azure: eu.gcr.io/gardener-project/gardener/extensions/validator-azure:v1.13.1

v1.13.0

[gardener-extension-provider-azure]

Most notable changes

• [USER] The Azure extension does now support shoot clusters with Kubernetes version 1.19. You should consider the Kubernetes release notes before upgrading to 1.19. (#157, @rfranzke)

Improvements

• [OPERATOR] The volumeBindingMode of the StorageClasses managed by Gardener is now switched to WaitForFirstConsumer. (#159, @ialidzhikov)

[cloud-provider-azure]

Improvements

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

[terraformer]

Improvements

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

Docker Images

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

v1.12.0

[gardener-extension-provider-azure]

Improvements

• [OPERATOR] The remedy controller is now enabled by default on all Azure clusters. It can be disabled using the annotation azure.provider.extensions.gardener.cloud/disable-remedy-controller: "true" (#151, @stoyanr)
• [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. (#149, @vpnachev)
• [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. (#147, @rfranzke)
• [OPERATOR] kubernetes-sigs/azuredisk-csi-driver is now updated to v0.8.0. (#146, @ialidzhikov)

[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-azure: eu.gcr.io/gardener-project/gardener/extensions/provider-azure:v1.12.0
gardener-extension-validator-azure: eu.gcr.io/gardener-project/gardener/extensions/validator-azure:v1.12.0

v1.11.0

[gardener-extension-provider-azure]

Most notable changes

• [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. (#124, @Kristian-ZH)

Improvements

• [USER] StorageClasses now allow for expansion of PVCs. (#133, @mvladev)
• [USER] The csi-node-driver daemon sets are now auto-scaled by the VPA in case the Shoot sets .spec.kubernetes.verticalPodAutoscaler.enabled=true. (#121, @rfranzke)
• [OPERATOR] Worker extension allows configuring following parameters on machine-deployment: drainTimeout, creationTimeout, healthTimeout, maxEvictRetries, nodeConditions. (#144, @hardikdr)
• [OPERATOR] The default webhook server port is now changed to 10250. (#143, @stoyanr)
• [OPERATOR] CSI controllers / drivers are now deployed by default if the Kubernetes version is 1.20 or later (not 1.19 as before) (#142, @stoyanr)
• [OPERATOR] kubernetes-sigs/azurefile-csi-driver is now updated to v0.8.0. (#140, @ialidzhikov)
• [OPERATOR] The controlplane controller now ensures that all remaining remedy controller resources have been deleted before deleting the remedy controller itself. (#138, @stoyanr)
• [OPERATOR] An issues has been fixed which caused unsuccessful shoot deletions due to the migration of the cloud-provider-config from a config map to a secret. (#131, @timuthy)
• [OPERATOR] Azure Storage Service Accounts for ETCD backup now have allowBlobPublicAccess set to false. See Azure Storage API for more details. (#129, @mvladev)

[cloud-provider-azure]

Improvements

• [OPERATOR] k8s.io/legacy-cloud-providers is now updated to v0.17.9. (gardener-attic/cloud-provider-azure#2, @ialidzhikov)
• [OPERATOR] k8s.io/legacy-cloud-providers is now updated to v0.18.6. (gardener-attic/cloud-provider-azure#3, @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)
• [OPERATOR] Added an option to use configDrive in the OpenStackMachineClass (gardener/machine-controller-manager#457, @zuzzas)
• [DEVELOPER] Increased default concurrent worker syncs from 5 --> 10 (gardener/machine-controller-manager#491, @prashanth26)
• [DEVELOPER] Bugfix: Drain machines with only a valid node (name) (gardener/machine-controller-manager#480, @prashanth26)

Docker Images

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

v1.10.1

[gardener-extension-provider-azure]

Improvements

• [OPERATOR] An issues has been fixed which caused unsuccessful shoot deletions due to the migration of the cloud-provider-config from a config map to a secret. (8ab1e78)

Docker Images

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

v1.10.0

Docker Images

gardener-extension-provider-azure: eu.gcr.io/gardener-project/gardener/extensions/provider-azure:v1.10.0
gardener-extension-validator-azure: eu.gcr.io/gardener-project/gardener/extensions/validator-azure:v1.10.0

v1.9.0

[gardener-extension-provider-azure]

Most notable changes

• [USER] It is now possible to configure additional data volumes for the worker machines. Please consult this documentation for more information. (#107, @rfranzke)
• [USER] Accelerated Networking feature has been disabled for AvSet clusters. It is still available for zoned clusters. (#100, @vpnachev)
• [OPERATOR] Until now provider-azure was maintaining a Terraform configuration which is both v0.12 and v0.11 compatible. The Terraform configuration is now adapted to the new Terraform language which makes it Terraform v0.11 incompatible. (#118, @ialidzhikov)

Improvements

• [USER] A bug has been fixed, that caused the Infrastructure not to be deleted for newly created clusters. (#113, @tim-ebert)
• [OPERATOR] A bug has been fixed, that caused the Infrastructure deletion to be blocked forever in case there are already running terraformer Pods. (#123, @tim-ebert)
• [OPERATOR] The Azure controlplane now contains an additional controller for applying "remedies" for certain sporadic Azure issues. (#120, @stoyanr)
• [OPERATOR] An issue has been fixed which caused a reconcile error for the infrastructure if the countFaultDomains or countUpdateDomains values for the shoot's region was changed. (#111, @timuthy)
• [OPERATOR] An issue preventing extensionsv1alpha1.BackupEntry to be deleted is now fixed. (#105, @ialidzhikov)
• [OPERATOR] Kubernetes dependencies are updated to v0.17.6. (#104, @ialidzhikov)
• [OPERATOR] The Kubernetes Kind for cloud-provider-config and cloud-provider-disk-config in a shoot's control plane has been changed from ConfigMap to Secret. (#99, @timuthy)
• [OPERATOR] An issue preventing error codes to be properly populated in .status.lastError.codes for Infrastructure is now fixed. (#97, @ialidzhikov)

[gardener]

Improvements

• [OPERATOR] Fixed a bug that lead to omitting the details message why a health check failed when writing the Extension CRD conditions. (gardener/gardener#2394, @danielfoehrKn)

[machine-controller-manager]

Most notable changes

• [DEVELOPER] Support for external / OOT (Out Of Tree) machine controller. A new provider can be maintained out of the core MCM repository. (gardener/machine-controller-manager#460, @prashanth26)

Improvements

• [OPERATOR] Azure: Fixes regression when using a VM image resource id instead of an URN (for example an image from a shared image gallery) (gardener/machine-controller-manager#475, @MSSedusch)
• [OPERATOR] CRDs are now generated with full OpenAPI schema. (gardener/machine-controller-manager#471, @mvladev)
• [OPERATOR] Enable support of snapshot-based volumes for machines in AWS. (gardener/machine-controller-manager#464, @hardikdr)

[terraformer]

Most notable changes

• [OPERATOR] Terraform version has been upgraded to 0.12.20. (gardener/terraformer#39, @minchaow)

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)
• [OPERATOR] The OpenStack terraform provider is now used in version v1.28.0. (gardener/terraformer#41, @dkistner)
• [OPERATOR] Provider alicloud version has been upgraded to 1.84.0. (gardener/terraformer#39, @minchaow)

Docker Images

gardener-extension-provider-azure: eu.gcr.io/gardener-project/gardener/extensions/provider-azure:v1.9.0
gardener-extension-validator-azure: eu.gcr.io/gardener-project/gardener/extensions/validator-azure:v1.9.0

v1.8.4

[gardener-extension-provider-azure]

Improvements

• [OPERATOR] An issue has been fixed which caused a reconcile error for the infrastructure if the countFaultDomains or countUpdateDomains values for the shoot's region was changed. (#112, @timuthy)

v1.8.3

[gardener-extension-provider-azure]

Improvements

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

Docker Images

gardener-extension-provider-azure: eu.gcr.io/gardener-project/gardener/extensions/provider-azure:v1.8.3
gardener-extension-validator-azure: eu.gcr.io/gardener-project/gardener/extensions/validator-azure:v1.8.3