mirrors/kyverno
mirrors/kyverno
1
0
Fork 0
mirror of https://github.com/kyverno/kyverno.git synced 2025-03-09 09:26:54 +00:00
Code Activity
kyverno/test/conformance/chainsaw/exceptions/exclude-seccomp
History
gcp-cherry-pick-bot[bot] 1e46816e00
chore: bump chainsaw (#11161) (#11177) 
* chore: bump chainsaw



* more template use



* v0.2.10



* go mod



---------

Signed-off-by: Charles-Edouard Brétéché <charles.edouard@nirmata.com>
Co-authored-by: Charles-Edouard Brétéché <charles.edouard@nirmata.com>
2024-09-17 10:09:15 +00:00
..
chainsaw-test.yaml chore: bump chainsaw (#11161) (#11177) 2024-09-17 10:09:15 +00:00
exception.yaml chore: use v2 for exceptions in chainsaw tests (#10529) 2024-06-24 11:54:57 +00:00
ns.yaml feat: add chainsaw tests for pod security in exceptions (#9667) 2024-02-06 13:07:58 +00:00
pod-allowed-1.yaml feat: add chainsaw tests for pod security in exceptions (#9667) 2024-02-06 13:07:58 +00:00
pod-allowed-2.yaml feat: add chainsaw tests for pod security in exceptions (#9667) 2024-02-06 13:07:58 +00:00
pod-rejected-1.yaml feat: add chainsaw tests for pod security in exceptions (#9667) 2024-02-06 13:07:58 +00:00
pod-rejected-2.yaml feat: add chainsaw tests for pod security in exceptions (#9667) 2024-02-06 13:07:58 +00:00
policy-assert.yaml feat: add chainsaw tests for pod security in exceptions (#9667) 2024-02-06 13:07:58 +00:00
policy.yaml chore: rename validationFailureAction to failureAction under the rule (#10893) 2024-08-27 20:07:57 +00:00
README.md feat: add chainsaw tests for pod security in exceptions (#9667) 2024-02-06 13:07:58 +00:00

README.md

Description

This test creates a policy that enforces the baseline profile and a policy exception that exempts any pod in the staging-ns namespace and sets the spec.securityContext.seccompProfile.type to Unconfined.

Steps

    • Create a cluster policy
    • Assert the policy becomes ready
    • Create a policy exception for the cluster policy created above.
    • Try to create a pod named good-pod-1 in the default namespace that doesn't violate the baseline profile, expecting the creation to succeed.
    • Try to create a pod named good-pod-2 in the staging-ns namespace and the spec.securityContext.seccompProfile.type is set to Unconfined and the spec.containers[*].securityContext.seccompProfile.type is set to RuntimeDefault, expecting the creation to succeed.
    • Try to create a pod named bad-pod-1 in the staging-ns namespace and the spec.securityContext.seccompProfile.type is set to Unconfined and the spec.containers[*].securityContext.seccompProfile.type is set to Unconfined, expecting the creation to fail.
    • Try to create a pod named bad-pod-2 in the default namespace and the spec.securityContext.seccompProfile.type is set to Unconfined and the spec.containers[*].securityContext.seccompProfile.type is set to Unconfined, expecting the creation to fail.