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 seccomp-psp-policy to target high level resources #25

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

Update policy seccomp-psp-policy to target high level resources #25

jvanz opened this issue Sep 23, 2022 · 2 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 seccomp-psp-policy Update policy seccomp-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
@niheetes
Copy link

This is an issue we see too. It would be really good for the policies to check pod started by higher level objects like deployments, statefulsets and so on.

Is this something on the planning to be looked at / picked up?

@jvanz
Copy link
Member Author

jvanz commented Jan 18, 2024

So far, we are not planning to work on that. However, as you are interested on this. I've added this issue to the Kubewarden board and I'll bring this issue to discussion in our next planning/daily call. I let you know about that asap.

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
Status: No status
Development

No branches or pull requests

2 participants