[ci:component:github.com/gardener/gardener-extension-provider-azure:v1.24.0->v1.26.2]

[gardener-robot-ci-2]

Release Notes:

An issue preventing load balancers from being functional for K8s 1.23 clusters has been fixed.

typo stopping scaleDown disabling during cluster rollout is fixed

The `terraformer` pod deployed as part of shoot control planes is now using auto-rotated `ServiceAccount` tokens when communicating with the seed cluster.

An integration test for user provided ip addresses for the NatGateway has been added.

Fixes a bug in the terraform manifest generation when more than one public IP Addresses were provided for the NAT Gateway

The CPU limit of `csi-driver-node/csi-driver` is increased from 50m to 100m to allow bigger bursts.

`gardener-extension-admission-azure` now supports configuration for enabling service account token volume projection. It is exposed through the `.Values.global.serviceAccountTokenVolumeProjection` section in the respective chart's values.

It is now possible to configure a `user` instead of a `serviceaccount` subject in the `clusterrolebinding` for the `gardener-extension-admission-azure` when using virtual garden setup by setting `.Values.global.virtualGarden.user.name`.

The Azure extension does now support shoot clusters with Kubernetes version 1.23. You should consider the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.23.md) before upgrading to 1.23.

machineDeployment will have the label `topology.disk.csi.azure.com/zone` when created if the shoot has csi enabled

This extension does now support `gardener/gardener`'s `WorkerPoolKubernetesVersion` feature gate, i.e., having [worker pools with overridden Kubernetes versions](https://github.com/gardener/gardener/blob/8a9c88866ec5fce59b5acf57d4227eeeb73669d7/example/90-shoot.yaml#L69-L70).

In case `gardener/gardener`'s `WorkerPoolKubernetesVersion` feature gate is enabled, it's possible having [worker pools with overridden Kubernetes versions](https://github.com/gardener/gardener/blob/8a9c88866ec5fce59b5acf57d4227eeeb73669d7/example/90-shoot.yaml#L69-L70) for `Shoot`s whose `.spec.kubernetes.version` is greater or equal than the CSI migration version (`1.21`).

The following terraform provider plugin is updated:
- `aliyun/terraform-provider-alicloud`: `1.124.2` -> `1.149.0`

The following terraform provider plugins are updated:
- hashicorp/terraform-provider-aws: 3.63.0 -> 3.66.0

terraform has been upgraded to 0.14.11

orphan collection is also triggered if machine obj is updated with having multiple backing VMs

Updated golang version to v1.17

The default leader election resource lock of `machine-controller-manager` has been changed from `endpoints` to `endpointsleases`.

Components that deploy the `machine-controller-manager` will now have to adapt the RBAC rules to allow `machine-controller-manager` to maintain its leader election resource lock in `leases` as well.

The extension controller uses a projected `ServiceAccount` token in case it runs on a seed with a gardenlet of at least `v1.37` or higher. Similarly, the components deployed into shoot namespaces will no longer use a client certificate but an auto-rotated `ServiceAccount` token which is only valid for `12h`.

Handle extensionsv1alpha1.Bastion resources for SSH access to worker instances

Azure provider now supports a new network setup that allows for zone redundant NAT Gateways.

`k8s.io/legacy-cloud-providers` is now updated to `v0.22.6`.

`k8s.io/legacy-cloud-providers` is now updated to `v0.21.9`.

`k8s.io/legacy-cloud-providers` is now updated to `v0.20.15`.

[gardener-robot]

@gardener-robot-ci-2 Thank you for your contribution.