mirrors/kyverno
mirrors/kyverno
1
0
Fork 0
mirror of https://github.com/kyverno/kyverno.git synced 2025-03-09 17:37:12 +00:00
Code Activity
kyverno/test/conformance/chainsaw/webhook-configurations/match-conditions-userinfo
History
Mariam Fahmy 2140a0239b
chore: rename validationFailureAction to failureAction under the rule (#10893) 
Signed-off-by: Mariam Fahmy <mariam.fahmy@nirmata.com>
Co-authored-by: Jim Bugwadia <jim@nirmata.com>
2024-08-27 20:07:57 +00:00
..
chainsaw-test.yaml feat: apply .matchConditions when generating reports (#9599) 2024-02-02 08:32:28 +00:00
ns.yaml feat: apply .matchConditions when generating reports (#9599) 2024-02-02 08:32:28 +00:00
pod.yaml feat: apply .matchConditions when generating reports (#9599) 2024-02-02 08:32:28 +00:00
policy-assert.yaml feat: apply .matchConditions when generating reports (#9599) 2024-02-02 08:32:28 +00:00
policy.yaml chore: rename validationFailureAction to failureAction under the rule (#10893) 2024-08-27 20:07:57 +00:00
README.md feat: apply .matchConditions when generating reports (#9599) 2024-02-02 08:32:28 +00:00
report-error-1.yaml feat: apply .matchConditions when generating reports (#9599) 2024-02-02 08:32:28 +00:00
report-error-2.yaml feat: apply .matchConditions when generating reports (#9599) 2024-02-02 08:32:28 +00:00

README.md

Description

This test creates a policy with matchConditions and two pods, it then expects a background scan report to be created for the pod in the selected namespace match-conditions-standard-ns other than default.

Steps

    • Create the testing namespace match-conditions-standard-ns
    • Create pods in match-conditions-standard-ns and default namespaces
    • Create a cluster policy
    • Assert the policy becomes ready
    • Assert a policy report is created for the pod in match-conditions-standard-ns
    • Assert a policy report is not created for the pod in default