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

Add configuration flag for pod_security_policy_config #140

Closed
bgeesaman opened this issue Apr 17, 2019 · 5 comments
Closed

Add configuration flag for pod_security_policy_config #140

bgeesaman opened this issue Apr 17, 2019 · 5 comments
Labels
enhancement New feature or request

Comments

@bgeesaman
Copy link

https://www.terraform.io/docs/providers/google/r/container_cluster.html#enabled-2
But disabled by the default variable(s).

This would allow cluster operators to enable this feature to support policies that prevent pods from being able to mount the host filesystem, run in the host network and/or process namespace, and run as a privileged user.

See: https://www.qwiklabs.com/focuses/5158?parent=catalog for more bg info if desired.

@morgante
Copy link
Contributor

+1

1 similar comment
@kbroughton
Copy link

+1

@aaron-lane aaron-lane added the enhancement New feature or request label May 27, 2019
aaron-lane added a commit that referenced this issue Jun 13, 2019
Add configuration flag for `pod_security_policy_config` #140
@aaron-lane
Copy link
Contributor

Fixed by #163.

@chrislovecnm
Copy link
Contributor

@aaron-lane we only did this for private clusters. Not sure why. Public clusters love PSP too!

@chrislovecnm
Copy link
Contributor

See #188

CPL-markus pushed a commit to WALTER-GROUP/terraform-google-kubernetes-engine that referenced this issue Jul 15, 2024
CPL-markus pushed a commit to WALTER-GROUP/terraform-google-kubernetes-engine that referenced this issue Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants