1
0
Fork 0
mirror of https://github.com/kyverno/kyverno.git synced 2025-03-05 23:46:56 +00:00
kyverno/test/conformance/chainsaw/flags/standard/emit-events
Mariam Fahmy 90ac90b89f
feat: use the check block for checking CLI output in chainsaw tests (#9616)
Signed-off-by: Mariam Fahmy <mariam.fahmy@nirmata.com>
2024-02-05 14:59:19 +00:00
..
admission-controller-assert.yaml chore: all chainsaw tests (#9011) 2023-11-24 11:17:58 +01:00
admission-controller.yaml fix: omit events flag (#9572) 2024-01-30 23:41:13 +00:00
chainsaw-test.yaml feat: use the check block for checking CLI output in chainsaw tests (#9616) 2024-02-05 14:59:19 +00:00
event-assert.yaml chore: all chainsaw tests (#9011) 2023-11-24 11:17:58 +01:00
policy-assert.yaml chore: all chainsaw tests (#9011) 2023-11-24 11:17:58 +01:00
policy.yaml chore: all chainsaw tests (#9011) 2023-11-24 11:17:58 +01:00
README.md fix: omit events flag (#9572) 2024-01-30 23:41:13 +00:00
resource-fail.yaml chore: all chainsaw tests (#9011) 2023-11-24 11:17:58 +01:00
resource.yaml chore: all chainsaw tests (#9011) 2023-11-24 11:17:58 +01:00

Description

This test updates the deployment with flag --omitEvents=PolicyApplied set Then it creates a policy, and a resource. The resource is expected to be accepted. A PolicyApplied event should be created. Then it creates a respource that is expected to be rejected A PolicyViolation event should not be emitted as the flag does not include that.

Steps

  1. Update the deployment of admission controller to add this ar--omitEvents=PolicyApplied.
    • Create a policy
    • Assert the policy becomes ready
    • Create a resource,
    • Asset a PolicyApplied event is created
  2. Try creating a resource with a script that is expected to fail.
  3. Exit the script with 0 if it returns an error