-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Pods should have seccompProfile RuntimeDefault #4693
Copy link
Copy link
Closed
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Description
In my K8s 1.19 cluster which implements Pod Security Standards with default Restricted, I cannot deploy cert-manager.yaml from the releases, because in all three deployments, the PodSpec is missing:
securityContext:
seccompProfile:
type: RuntimeDefault
Expected behaviour:
Since cert-manager seems to still work when applying those security best-practices, it should just apply in a cluster like mine.
Environment details::
- Kubernetes version: 1.19
- Cloud-provider/provisioner: kubeadm on Debian 10
- cert-manager version: 1.6.1
- Install method: apply
cert-manager.yamlas kustomize resource
/kind bug
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.