Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API supports is too old to run 020-rbac.yaml #27

Open
humble92 opened this issue Jul 8, 2023 · 2 comments
Open

API supports is too old to run 020-rbac.yaml #27

humble92 opened this issue Jul 8, 2023 · 2 comments

Comments

@humble92
Copy link

humble92 commented Jul 8, 2023

PodSecurityPolicy has been removed since v1.25, so the error below occurs.

in 020-rbac.yaml

apiVersion: policy/v1
kind: PodSecurityPolicy

Error line:

error: resource mapping not found for name: "jitsi-privileged" namespace: "" from ".": no matches for kind "PodSecurityPolicy" in version "policy/v1"
ensure CRDs are installed first

@kskalski
Copy link

I was able to work-around this by adding

patches:
- path: 020-rbac.yaml

to kustomize.yaml and creating file 020-rbac.yaml with

$patch: delete
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
  name: jitsi-privileged

I'm not completely sure if the pod security policy should instead be replaced by some else.

@humble92
Copy link
Author

Yes, it works! Thanks a lot. @kskalski

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants