Greetings. Why could provisioning a fresh RKE2 cluster produce a completely broken setup? Anything that I try to deploy in any namespace besides the default ones ends up with "forbidden: PodSecurityPolicy: unable to admit pod: " without any sane explanation. Have tried deploying both v1.22.16 and v1.24.8 without any luck. Doesn't matter which default pod security policy is set - both unrestricted and RKE2 default fail. I'm out of ideas at this point.
solution has been found, RKE2 clusterrole configuration is broken out of the box
02/12/2023, 11:11 AM
how did you fix it, i am also getting the same issue while i am installing argocd on my production cluster.