v1.33.0

[gardener-extension-provider-openstack]

⚠️ Breaking Changes

• [USER] Adapt worker node hash calculation. Shoots that are currently using the server group feature will be rolled out. You can prevent the rollout if the shoot is annotated with openstack.provider.extensions.gardener.cloud/worker-preserve-hash. (gardener/gardener-extension-provider-openstack#602, @kon-angelo)

✨ New Features

• [USER] Optional CSI Manila driver deployment to support NFS persistent volumes out-of-the-box. (gardener/gardener-extension-provider-openstack#572, @MartinWeindel)
• [OPERATOR] csi-driver-node is annotated with the wait-for-csi-node annotation. Gardener uses this to only schedule workload pods to a Node once the driver has been successfully registered with the CSINode object. (gardener/gardener-extension-provider-openstack#583, @SimonKienzler)
• [OPERATOR] The csi-snapshot-validation Service deployed by the provider-openstack extension can now be topology-aware (depending on the Seed setting and the Shoot HA failure tolerance type). For more details, see the Topology-aware Traffic Routing documentation. (gardener/gardener-extension-provider-openstack#589, @ialidzhikov)

🐛 Bug Fixes

• [OPERATOR] The stale healthcheck conditions from the extension are now properly cleaned up. (gardener/gardener-extension-provider-openstack#590, @acumino)
• [OPERATOR] An issue has been fixed which caused undesired PATCH requests when updating the state in the Worker or ShootState resources. (gardener/gardener-extension-provider-openstack#597, @oliver-goetz)
• [OPERATOR] An issue causing provider-openstack to wrongly delete the extensions.gardener.cloud:provider-openstack:csi-snapshot-validation ClusterRole and ClusterRoleBinding from the Seed cluster on every Shoot deletion is now fixed. (gardener/gardener-extension-provider-openstack#603, @ialidzhikov)

🏃 Others

• [OPERATOR] Adapted extension components to support the FullNetworkPoliciesInRuntimeCluster feature gate introduced by gardener/gardener v1.66, see here and #7352 for more information. (gardener/gardener-extension-provider-openstack#578, @timuthy)
• [OPERATOR] Add machine labels to the ProviderConfig of a worker pool to support rolling of its machines on label changes. (gardener/gardener-extension-provider-openstack#579, @MartinWeindel)
• [OPERATOR] Add support for user-provided NodeTemplates (gardener/gardener-extension-provider-openstack#581, @kon-angelo)
• [OPERATOR] Switched images from DockerHub to copies in Gardener GCR (gardener/gardener-extension-provider-openstack#592, @robinschneider)
• [OPERATOR] provider-openstack does no longer use Gardener GCR copies for openstack-cloud-controller-manager and cinder-csi-plugin in versions 1.24, 1.25 and 1.26. Instead, the upstream GCR container images are used (registry.k8s.io/provider-os/openstack-cloud-controller-manager and registry.k8s.io/provider-os/cinder-csi-plugin). (gardener/gardener-extension-provider-openstack#593, @ialidzhikov)
• [OPERATOR] The following images are updated: (gardener/gardener-extension-provider-openstack#593, @ialidzhikov)
  • registry.k8s.io/provider-os/cinder-csi-plugin: v1.24.5 -> v1.24.6 (for Kubernetes 1.24 Shoots)
  • registry.k8s.io/provider-os/cinder-csi-plugin: v1.25.3 -> v1.25.5 (for Kubernetes 1.25 Shoots)
  • registry.k8s.io/provider-os/cinder-csi-plugin: v1.26.0 -> v1.26.2 (for Kubernetes 1.26 Shoots)
• [OPERATOR] Cloud-controller-manager Loadbalancer configuration has been updated: monitorDelay: 60s -> 20s, monitorMaxRetries: 5 -> 2 (gardener/gardener-extension-provider-openstack#594, @kon-angelo)
• [OPERATOR] The gardener-extension-admission-openstack Service in the gardener-extension-admission-openstack chart can now be configured to be topology-aware. (gardener/gardener-extension-provider-openstack#599, @ialidzhikov)

[machine-controller-manager]

🐛 Bug Fixes

• [USER] An edge case where all the machineSets were scaled down to zero has been dealt with. (gardener/machine-controller-manager#804, @himanshu-kun)

[terraformer]

🏃 Others

• [OPERATOR] Update TF_VERSION 0.15.5 -> 1.3.9 and update how the local providers are fetched and stored to be compatible with the latest TF specification. (gardener/terraformer#133, @kon-angelo)