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

Update policy volumes-psp-policy to target high level resources #11

Open
Tracked by #282
jvanz opened this issue Sep 23, 2022 · 3 comments
Open
Tracked by #282

Update policy volumes-psp-policy to target high level resources #11

jvanz opened this issue Sep 23, 2022 · 3 comments
Labels
good first issue Good for newcomers kind/enhancement New feature or request

Comments

@jvanz
Copy link
Member

jvanz commented Sep 23, 2022

Update the policy from targeting Pod resource to target higher level objects like deployments. This is a better practice because we prevent the resources to be created instead of failing in the deployment phase when the pods are created.

@jvanz jvanz changed the title volumes-psp-policy/ Update policy volumes-psp-policy to target high level resources Sep 23, 2022
@jvanz jvanz transferred this issue from kubewarden/kubewarden-controller Sep 23, 2022
@jvanz jvanz added kind/enhancement New feature or request good first issue Good for newcomers labels Oct 4, 2022
@adnanhashmi09
Copy link

Can you please assign this to me.

@jvanz
Copy link
Member Author

jvanz commented Aug 4, 2023

Can you please assign this to me.

Done!

@adnanhashmi09 adnanhashmi09 removed their assignment Aug 7, 2023
@adnanhashmi09
Copy link

Rather than making changes to individual policies, we might consider doing something like Kyverno aug-gen rules. This is being tracked here. I am going to create a PR against the RFC repo with a proposal about how to implement something similar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers kind/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants