3.36.0

[garden-setup]

⚠️ Breaking Changes

• [OPERATOR] Due to a current workaround in Gardener (see gardener/gardener@8c6399d), Gardener will delete all ingress resources in the garden namespace of the seed cluster when removing a seed. This causes problems with garden-setup, where the ingress for the virtual cluster is located in the garden namespace on the base cluster, which is also used as seed cluster. To prevent the deletion of this ingress until the kube-apiserver component is deleted, a finalizer has been added to it. However, the ingress will still get a deletionTimestamp, which blocks most changes to the resource from then on. Most users should not be affected by this, but if you partially delete a garden-setup landscape, including the gardencontent/seeds/soils component but excluding the kube-apiserver component, you might run into problems when trying to update the kube-apiserver component later on. (gardener/garden-setup#889, @Diaphteiros)

✨ New Features

• [OPERATOR] Upgrade Gardener to v1.53.4 (gardener/garden-setup#889, @Diaphteiros)

🏃 Others

• [OPERATOR] Upgrade Gardener extension runtime-gvisor to v0.6.0 (gardener/garden-setup#889, @Diaphteiros)