Install the Kyverno CLI: https://kyverno.io/docs/kyverno-cli/
Then run the Kyverno checks against the rendered workloads:
make kyverno-workloads The same render + validate steps run in the YAML Policy Check workflow "yaml-policy-check.yml"
Policies live in: .github/workflows/kyverno/policies/
The policy for the hardened Collector securityContextis here
It enforces the following container security settings:
securityContext.capabilities.drop: ["ALL"]securityContext.readOnlyRootFilesystem: truesecurityContext.allowPrivilegeEscalation: falsesecurityContext.runAsNonRoot: truesecurityContext.runAsUser: 10001securityContext.runAsGroup: 10001securityContext.privileged: falsesecurityContext.seccompProfile.type: RuntimeDefault
These are widely recommended Kubernetes hardening defaults. For background, see:
- Kubernetes Security Context docs: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
- Kubernetes Pod Security Standards: https://kubernetes.io/docs/concepts/security/pod-security-standards/
- This is an internal CI tool (not part of the shipped Collector artifacts).
- The Kyverno validation applies to the workloads/scenarios rendered and exercised by this repository’s CI. It is intended as a compatibility/regression check and a guardrail for new additions — not a blanket guarantee that every possible configuration of every component will work under all hardened Kubernetes policies.