[gardener-extension-provider-openstack]

✨ New Features

[USER] The OpenStack extension does now support shoot clusters with Kubernetes version 1.22. You should consider the Kubernetes release notes before upgrading to 1.22. (#330, @timuthy)
[OPERATOR] Floating pool names in infrastructure config are now checked if they exist, and if not the issue is properly reported as ERR_CONFIGURATION_PROBLEM with a clear error message. (#329, @stoyanr)
[OPERATOR] Add option ignoreVolumeAZ to allow for differences between volume and compute AZ names. (#322, @gesslein)

[USER] Do not trigger a node rollout when switching from CRI.Name==nil to CRI.Name==docker. (#308, @BeckerMax)

[USER] It is now allowed to change the name and purpose of load balancer classes in .controlPlaneConfig.loadBalancerClasses[]. The load balancer classes configuration need still to be semantically equal with the load balancer classes from the CloudProfile. (#310, @dkistner)
[OPERATOR] machine-controller-manager logs are exposed to the end-users (#319, @vlvasilev)
[OPERATOR] Shoots can now be deployed in existing Neutron networks. The network can be specified by its ID in the respective shoot's infrastructure configuration. (#317, @kon-angelo)
[OPERATOR] Openstack Kubernetes cluster >= v1.22 use now the Openstack cloud-controller-manager v1.22. (79d7412)
[OPERATOR] Openstack Kubernetes cluster >= v1.22 now use cinder csi v1.22. (79d7412)
[DEVELOPER] Missing or wrong doc comments and a few other common style errors will now be reported by the linter. (#334, @stoyanr)

[OPERATOR] Draining of pods with PVs (Persistent Volume) now waits for re-attachment of PV on a different node when volumeAttachments support is enabled on the cluster. Else it falls back to the default PV reattachment timeout value configured. The default value is 90s and this can be overwritten via the machine-pv-reattach-timeout flag. Please enable permissions to allow listing of volumeAttachments resource while importing these changes. (gardener/machine-controller-manager#608, @prashanth26)

[USER] Increase default concurrent object syncs to 50 to allow more concurrent reconciles to occur. (gardener/machine-controller-manager#629, @prashanth26)
[USER] Machine rollouts are now more as desired with the number of replicas always maintained to desired + maxSurge. Earlier machines in termination were left out of this calculation but now is considered with this change. (gardener/machine-controller-manager#627, @prashanth26)
[OPERATOR] Finalizers will be added to the MachineClass which is used by at least one machine. Machines whose backing MachineClass does not have finalizers shall not be reconciled. (gardener/machine-controller-manager#593, @AxiomSamarth)
[DEVELOPER] Replace integration test with unit test to test the functionality to freeze MachineSet (gardener/machine-controller-manager#620, @AxiomSamarth)

[OPERATOR] Avoids blocking of drain call when the buffer is full for the volumeAttachmentHandlers. (gardener/machine-controller-manager#627, @prashanth26)
[DEVELOPER] Test framework now fetches secrets from the correct (control) APIServer while running tests. (gardener/machine-controller-manager#617, @himanshu-kun)

[OPERATOR] Nodes attached to the cluster without MCM support are now annotated with "node.machine.sapcloud.io/notManagedByMCM": "1". This is then ignored by the MCM for further processing. (gardener/machine-controller-manager#612, @himanshu-kun)

[DEVELOPER] Once the azurerm provider plugin is updated from v2.36.0 to v2.68.0 the skip_provider_registration flag in the provider section need to be set to true. (gardener/terraformer#99, @dkistner)

[OPERATOR] The terraform azurerm provider plugin is updated from v2.36.0 to v2.68.0. (gardener/terraformer#99, @dkistner)
[OPERATOR] The following terraform provider plugins are updated: (gardener/terraformer#98, @ialidzhikov)
- hashicorp/terraform-provider-aws: 3.18.0 -> 3.32.0
[OPERATOR] The following terraform provider plugin is updated: (gardener/terraformer#96, @minchaow)
- aliyun/terraform-provider-alicloud: 1.124.0 -> 1.124.2