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.

Sign up for GitHub

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

Jump to bottom

Remove all PodSecurityPolcies, but allow for them to remain with experimental config #12314

Closed
mrsimonemms opened this issue Aug 23, 2022 · 0 comments · Fixed by #12336
Closed

Remove all PodSecurityPolcies, but allow for them to remain with experimental config #12314

mrsimonemms opened this issue Aug 23, 2022 · 0 comments · Fixed by #12336
Assignees
@mrsimonemms

Comments

@mrsimonemms
Copy link
Contributor

An incident was caused by #12173 - despite the testing, the SaaS cluster was configured to have the PodSecurityPolcies enabled and the GKE testing done did not (mea culpa - I thought it did).

As Kubernetes v1.25 removes support for PodSecurityPolicies, it is not an option to maintain these in the Installer for the long-term.

The proposal is to add a usePodSecurityPolicies bool in the experimental section of the config (defaulting to false) and to conditionally remove the resources removed in #12173.

As this is a deprecated feature in Kubernetes, the bool should be marked as deprecated from the start
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mrsimonemms mrsimonemms

Labels
None yet
Projects
No open projects
🚚 Security, Infrastructure, and Delivery Team (SID)
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[installer]: conditionally remove pod security policies gitpod-io/gitpod
1 participant
@mrsimonemms