1
0
Fork 0
mirror of https://github.com/kyverno/kyverno.git synced 2025-03-09 01:16:55 +00:00
kyverno/test/conformance/chainsaw/exceptions/exclude-host-process-and-host-namespaces
Charles-Edouard Brétéché df267dd829
chore: use more chainsaw step templates (#11311)
Signed-off-by: Charles-Edouard Brétéché <charles.edouard@nirmata.com>
2024-10-03 11:56:30 +00:00
..
chainsaw-test.yaml chore: use more chainsaw step templates (#11311) 2024-10-03 11:56:30 +00:00
exception.yaml chore: use v2 for exceptions in chainsaw tests (#10529) 2024-06-24 11:54:57 +00:00
ns.yaml feat: support podSecurity exclusion in exceptions (#9343) 2024-01-26 18:43:07 +00:00
pod-allowed-1.yaml feat: support podSecurity exclusion in exceptions (#9343) 2024-01-26 18:43:07 +00:00
pod-allowed-2.yaml feat: support podSecurity exclusion in exceptions (#9343) 2024-01-26 18:43:07 +00:00
pod-allowed-3.yaml feat: support podSecurity exclusion in exceptions (#9343) 2024-01-26 18:43:07 +00:00
pod-rejected.yaml feat: support podSecurity exclusion in exceptions (#9343) 2024-01-26 18:43:07 +00:00
policy.yaml chore: rename validationFailureAction to failureAction under the rule (#10893) 2024-08-27 20:07:57 +00:00
README.md feat: support podSecurity exclusion in exceptions (#9343) 2024-01-26 18:43:07 +00:00

Description

This test creates a policy that enforces the baseline profile and exempts any pod that violates the Host Namespaces control and a policy exception that exempts any pod that violates the HostProcess control. The policy exception is configured to apply only to the pods that in staging-ns-1 namespace.

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 goodpod-01 in the staging-ns-1 namespace that uses both the Host Namespace and the HostProcess controls, expecting the creation to succeed.
    • Try to create a pod named goodpod-02 in the staging-ns-1 namespace that uses the HostProcess control, expecting the creation to succeed.
    • Try to create a pod named goodpod-03 in the default namespace that uses the Host Namespace control, expecting the creation to succeed.
    • Try to create a pod named badpod-01 in the default namespace that uses both the Host Namespace and the HostProcess controls, expecting the creation to fail.