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

PodSecurityPolicy removed from K8s 1.25 #459

Open
ramessesii2 opened this issue Sep 5, 2022 · 0 comments · May be fixed by #598
Open

PodSecurityPolicy removed from K8s 1.25 #459

ramessesii2 opened this issue Sep 5, 2022 · 0 comments · May be fixed by #598

Comments

@ramessesii2
Copy link

Description

PodSecurityPolicy which was initially deprecated with K8s 1.21 has now been completely removed with K8s 1.25.

What's next

Now, Namespaces can be labeled to enforce the Pod Security Standards. The three policies privileged, baseline and restricted broadly cover the security spectrum and are implemented by the Pod Security admission controller.

Proposal

To be able to successfully transition to K8s 1.25 (#457), we'll need to make changes accordingly to this repo.
I'm not sure if there are already plans for it. If so, please add the research/info here and if no one else is looking into it, I can take on it.

@rumstead rumstead linked a pull request Jul 2, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant