Unable to install gardener in 1.26.2 k8s cluster

[lusche]

What happened:
We tried to install gardener using the following documentation https://github.com/gardener/garden-setup#readme into a fresh 1.26.2 k8s cluster. The installer failed very early with the following error:

Running helm template for garden-setup-dns-controller-manager ...
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /mounted/customers/Boreus/dev/temp/gardener/landscape/gen/dns-controller/helm/kubeconfig
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /mounted/customers/Boreus/dev/temp/gardener/landscape/gen/dns-controller/helm/kubeconfig
using config from path kubectl_apply
Plugin: kubectl[deploy]{kubectl_apply} (/sow/plugins/kubectl/plugin)
manifest for PodSecurityPolicy(policy/v1beta1): kube-system/garden-setup-dns-controller-manager
error: unable to recognize "/mounted/customers/Boreus/dev/temp/gardener/landscape/gen/dns-controller/kubectl_apply/manifests/0-0-PodSecurityPolicy.kube-system.garden-setup-dns-controller-manager.yaml": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1"
command failed, waiting for 15 seconds and trying again (4 times)

I'm unable to find a hint in the documentation howto disable psp. Since 1.26 didn't support this feature anymore

What you expected to happen:
That I'm able to install gardener into an 1.26 k8s cluster

How to reproduce it (as minimally and precisely as possible):
try to follow the steps in the linked dokumentation and use an 1.26.* clsuter as target

Anything else we need to know?:

Environment:

• Version of garden-setup: TAG 3.47.0
• Versions of components: defaults
• Where does the underlying base cluster come from and which operating system does it use?

NAME                               STATUS   ROLES           AGE    VERSION    EXTERNAL-IP   OS-IMAGE                           KERNEL-VERSION                 CONTAINER-RUNTIME
gardener-mgmt-master-0.novalocal   Ready    control-plane   147m   v1.26.2    <none>        Rocky Linux 8.7 (Green Obsidian)   4.18.0-425.13.1.el8_7.x86_64   containerd://1.6.18
gardener-mgmt-master-1.novalocal   Ready    control-plane   146m   v1.26.2    <none>        Rocky Linux 8.7 (Green Obsidian)   4.18.0-425.13.1.el8_7.x86_64   containerd://1.6.18
gardener-mgmt-master-2.novalocal   Ready    control-plane   146m   v1.26.2    <none>        Rocky Linux 8.7 (Green Obsidian)   4.18.0-425.13.1.el8_7.x86_64   containerd://1.6.18
gardener-mgmt-worker-0.novalocal   Ready    <none>          145m   v1.26.2    <none>        Rocky Linux 8.7 (Green Obsidian)   4.18.0-425.13.1.el8_7.x86_64   containerd://1.6.18
gardener-mgmt-worker-1.novalocal   Ready    <none>          145m   v1.26.2    <none>        Rocky Linux 8.7 (Green Obsidian)   4.18.0-425.13.1.el8_7.x86_64   containerd://1.6.18
gardener-mgmt-worker-2.novalocal   Ready    <none>          145m   v1.26.2    <none>        Rocky Linux 8.7 (Green Obsidian)   4.18.0-425.13.1.el8_7.x86_64   containerd://1.6.18

• Which cloud provider is configured for the setup: Openstack
• Other:

[Diaphteiros]

Sorry, I completely missed this issue.

However, I roughly remember having fixed this some time ago. The problem here was that k8s promoted the PSP to another version (v1, I guess).

I can setup a Gardener landscape on a 1.26 cluster, so it should not be an issue anymore.