-
Notifications
You must be signed in to change notification settings - Fork 315
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
[Feature] Support setting seccompDefault #3552
Comments
FYI the feature flag should be on by default in Kubernetes 1.27. kubernetes/enhancements#2413 |
Action required from @Azure/aks-pm |
Issue needing attention of @Azure/aks-leads |
13 similar comments
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
See #3722 |
Is your feature request related to a problem? Please describe.
I would like to be able to change the default seccomp profile from
Unconfined
toRuntimeDefault
Describe the solution you'd like
Allow setting
seccompDefault
, see https://kubernetes.io/blog/2021/08/25/seccomp-default/#seccompdefault-to-the-rescueDescribe alternatives you've considered
Set it manually for every workload
The text was updated successfully, but these errors were encountered: