Releases: gardener/gardener-extension-provider-azure
v1.15.1
[gardener-extension-provider-azure]
🏃 Others
- [OPERATOR] The gen-provider-azure TestDefinition is now passing the correct flag to the generator. (fa3b517)
Docker Images
gardener-extension-provider-azure: eu.gcr.io/gardener-project/gardener/extensions/provider-azure:v1.15.1
gardener-extension-validator-azure: eu.gcr.io/gardener-project/gardener/extensions/validator-azure:v1.15.1
v1.15.0
[gardener-extension-provider-azure]
⚠️ Breaking Changes
- [OPERATOR] Operators need to ensure that all Azure Shoot
Infrastructureresource are reconciled with the Gardener Azure provider extensionv1.14.0(contains a PR which is a prerequisite for this Terraform migration #161) before applying this version. Please have a special look on hibernated clusters as theirInfrastructureis might not reconciled for a while. (#192, @dkistner) - [OPERATOR] In v1.9.0 gardener-extension-provider-azure switched the kind for
cloud-provider-configandcloud-provider-disk-configin the Shoot control plane from ConfigMap to Secret (ref #99). In this version of gardener-extension-provider-azure the corresponding cleanup and graceful migration logic related to this switch is removed. Before upgrading to this version of gardener-extension-provider-azure, make sure that you have first upgraded to v1.9.0 or newer version and the kind forcloud-provider-configandcloud-provider-disk-configis migrated to Secret. (#187, @ialidzhikov)
🏃 Others
- [OPERATOR] gardener-extension-provider-azure does now have a health check for the remedy-controller Deployment. (#203, @ialidzhikov)
- [OPERATOR] The Gardener Azure provider extension is now using the
azurermTerraform provider in versionv2.x.x(#192, @dkistner) - [OPERATOR] Golang version is updated to
1.15and alpine image version is updated to3.12.1. (#185, @kon-angelo) - [OPERATOR] Adds priority class for extension pods to prevent preemption. (#181, @danielfoehrKn)
- [DEVELOPER] An issue causing
make testto fail on macOS is now fixed. (#188, @ialidzhikov) - [DEVELOPER] The client management for various Azure services within the Azure provider extension has been harmonised by adding a factory to produce those clients. (#186, @dkistner)
📰 Noteworthy
- [OPERATOR] The infrastructure actuator is now injecting infrastructure credentials into the terraformer
PodSpecvia secret references instead of plain env var values. (#196, @timebertt) - [DEVELOPER] The infrastructure integration test can now be triggered on a PR by commenting
/testinstead of/test-single. (#202, @timebertt)
[machine-controller-manager]
🏃 Others
- [USER] The default drainTimeout value has been updated from 12hours to 2hours. (gardener/machine-controller-manager#554, @prashanth26)
- [USER] OOT: Fixed regression with maxEvictRetries (gardener/machine-controller-manager#554, @prashanth26)
- [USER] Adds the ability to specify an already existing OpenStack Neutron network in the subnetID of an OpenStackMachineClass. MCM will deploy new machines into the given subnet by pre-allocating Neutron ports and pass them to the Nova server object. (gardener/machine-controller-manager#545, @MrBatschner)
- [USER] The machine-controller-manager supports now machines attached to Azure VirtualMachineScaleSet Orchestration Mode VM (VMO). (gardener/machine-controller-manager#519, @dkistner)
- [USER] Restored tag verification in the Azure driver to filter VMs/disks/NICs based on tags (gardener/machine-controller-manager#507, @zuzzas)
- [OPERATOR] An issue causing panic when the encoded machine template hash length is less than expect limit is now fixed. (gardener/machine-controller-manager#577, @AxiomSamarth)
- [OPERATOR] Set Machine Phase to Terminating before draining. (gardener/machine-controller-manager#564, @prashanth26)
- [OPERATOR] Allow migration to continue when ProviderMachineClass is missing but MachineClass with the same name as ProviderMachineClass is found. Updates Machine object references to the MachineClass. (gardener/machine-controller-manager#559, @prashanth26)
- [OPERATOR] Use cache-based listers to GET the machine-object while reconciling. (gardener/machine-controller-manager#558, @hardikdr)
- [OPERATOR] OOT: Enqueue machine only when node conditions have changed. (gardener/machine-controller-manager#557, @prashanth26)
- [OPERATOR] Adapted integration tests to handle possibly orphaned resources. (gardener/machine-controller-manager#550, @hardikdr)
- [OPERATOR] OOT: Fixes drain timeout issues on retires (gardener/machine-controller-manager#548, @prashanth26)
- [OPERATOR] NetworkUnavailable nodeCondition added to the example, some CNI will update this condition depending on the state of the CNI or the network availability. (gardener/machine-controller-manager#543, @rewiko)
- [OPERATOR] Added a more comprehensive set of events to trigger machine class reconciliations. (gardener/machine-controller-manager#531, @prashanth26)
- [OPERATOR] Finalizers are added by default for all machine class objects. (gardener/machine-controller-manager#531, @prashanth26)
- [OPERATOR] Bootstrap token injection now works in the new OOT Machine controller (gardener/machine-controller-manager#521, @zuzzas)
- [OPERATOR] Add support for ServerGroups in the Openstack driver. VMs can now be created in the ServerGroup specified in the respective
MachineClass. (gardener/machine-controller-manager#511, @kon-angelo) - [OPERATOR] Bugfix: Consider CSI PersistentVolumes during the eviction of Pods with PersistentVolumes. (gardener/machine-controller-manager#509, @ialidzhikov)
- [DEVELOPER] Adds a new phase
CrashLoopBackOffthat is set due to machine creation failures. (gardener/machine-controller-manager#525, @hardikdr) - [DEVELOPER] The field
availabilitySetsin theAzureMachineClassis now deprecated in favour of the fieldmachineSet, which allow to configure AvailabilitySets and VirtualMachineScaleSet Orchestration Mode VM (VMO). The field will be removed in the future. (gardener/machine-controller-manager#519, @dkistner)
📰 Noteworthy
- [USER] NetworkUnavailable node condition is also considered by default while considering the machine's to be unhealthy. (gardener/machine-controller-manager#543, @rewiko)
- [USER] AWS: Allows deletion of machines even on modify instance call failure (gardener/machine-controller-manager#515, @prashanth26)
- [OPERATOR] Machine force deletion computation is based on deletionTimestamp instead of LastUpdatedTimestamp. (gardener/machine-controller-manager#564, @prashanth26)
- [OPERATOR] OOT: Introduced a backoff in re-enqueuing machines on creation/deletion failures. Avoids throttling APIServer & provider calls. (gardener/machine-controller-manager#557, @prashanth26)
- [OPERATOR] Introduced a backoff in re-enqueuing machines on creation/deletion failures. Avoids throttling APIServer & provider calls. (gardener/machine-controller-manager#525, @hardikdr)
[terraformer]
🏃 Others
- [OPERATOR] Terraformer uses now the azurerm provider in version v2.36.0 (gardener/terraformer#54, @dkistner)
Docker Images
gardener-extension-provider-azure: eu.gcr.io/gardener-project/gardener/extensions/provider-azure:v1.15.0
gardener-extension-validator-azure: eu.gcr.io/gardener-project/gardener/extensions/validator-azure:v1.15.0
v1.14.1
[gardener-extension-provider-azure]
Most notable changes
- [USER] Fixes issues where machines were force deleted during normal deletion due to a race condition. (#200, @prashanth26)
[machine-controller-manager]
Most notable changes
- [OPERATOR] Machine force deletion computation is based on deletionTimestamp instead of LastUpdatedTimestamp. (gardener/machine-controller-manager#564, @prashanth26)
Improvements
- [OPERATOR] Set Machine Phase to Terminating before draining. (gardener/machine-controller-manager#564, @prashanth26)
Docker Images
gardener-extension-provider-azure: eu.gcr.io/gardener-project/gardener/extensions/provider-azure:v1.14.1
gardener-extension-validator-azure: eu.gcr.io/gardener-project/gardener/extensions/validator-azure:v1.14.1
v1.14.0
[gardener-extension-provider-azure]
Improvements
- [OPERATOR]
github.com/gardener/gardenerdependency is now updated tov1.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
minAllowedvalues for VPA
- [OPERATOR] Add common certificate directory mounts to the CCM. (#167, @danielfoehrKn)
- [OPERATOR]
kubernetes-sigs/azuredisk-csi-driveris now updated tov0.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-providersis now updated tov0.17.13. (gardener-attic/cloud-provider-azure@9e40e1f) - [OPERATOR]
k8s.io/legacy-cloud-providersis now updated tov0.18.10. (gardener-attic/cloud-provider-azure@e983941) - [OPERATOR]
k8s.io/legacy-cloud-providersis now updated tov0.19.3. (gardener-attic/cloud-provider-azure@4d96697)
[gardener]
Most notable changes
- [OPERATOR] Machines without
.spec.providerIDor.status.nodewill no longer be persisted in theWorker'.status.statefield. This is to prevent unnecessary updates to theShootStateresources. (gardener/gardener#2909, @rfranzke)
[machine-controller-manager]
Most notable changes
- [USER] Support for Spot Instances is available in AWS driver. If the
spotPriceis 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/statusresources. (gardener/machine-controller-manager#492, @guydaichs) - [OPERATOR] New flag
delete-migrated-machine-classis 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-rolloutis introduced to disable annotating the nodes with cluster-autoscaler annotationcluster-autoscaler.kubernetes.io/scale-down-disabledduring rollout. (gardener/machine-controller-manager#496, @hardikdr) - [DEVELOPER] Adds a new phase
CrashLoopBackOffthat 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.providerIDor.status.nodewill no longer be persisted in theWorker'.status.statefield. This is to prevent unnecessary updates to theShootStateresources. (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
volumeBindingModeof the StorageClasses managed by Gardener is now switched toWaitForFirstConsumer. (#159, @ialidzhikov)
[cloud-provider-azure]
Improvements
- [OPERATOR]
k8s.io/legacy-cloud-providersis now updated tov1.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-alicloudis now updated to1.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
PodDisruptionBudgetfor the validation server is now automatically deployed as part of its Helm chart if the replica count is larger than1. (#147, @rfranzke) - [OPERATOR]
kubernetes-sigs/azuredisk-csi-driveris now updated tov0.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
Loggingfeature 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 theLoggingfeature gate is enabled. (#124, @Kristian-ZH)
Improvements
- [USER]
StorageClassesnow allow for expansion of PVCs. (#133, @mvladev) - [USER] The
csi-node-driverdaemon 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-driveris now updated tov0.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-configfrom a config map to a secret. (#131, @timuthy) - [OPERATOR] Azure Storage Service Accounts for ETCD backup now have
allowBlobPublicAccessset tofalse. See Azure Storage API for more details. (#129, @mvladev)
[cloud-provider-azure]
Improvements
- [OPERATOR]
k8s.io/legacy-cloud-providersis now updated tov0.17.9. (gardener-attic/cloud-provider-azure#2, @ialidzhikov) - [OPERATOR]
k8s.io/legacy-cloud-providersis now updated tov0.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-configfrom 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