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

Create an "Enforce on all Pods" option for Seccomp Profile Bindings #1868

Closed
CoreyCook8 opened this issue Sep 6, 2023 · 0 comments · Fixed by #1869
Closed

Create an "Enforce on all Pods" option for Seccomp Profile Bindings #1868

CoreyCook8 opened this issue Sep 6, 2023 · 0 comments · Fixed by #1869
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@CoreyCook8
Copy link
Contributor

What would you like to be added:

Logic would be added to the Handle function to look for a container name * for example and then apply the seccomp profile to the pod.

This could could be scaled back through webhookOptions if there are exceptions within a namespace.

Why is this needed:

Profile Bindings are good for enforcing specific seccomp profiles on specific containers.

Applying a default seccomp profile is not realistic with the way they are set up currently.

User story covered

As a developer, I would like to define a default seccomp profile to be applied to each pod in my namespace so that I can ensure the pods running in my cluster are secure without having to make profile bindings for each container.

@CoreyCook8 CoreyCook8 added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant