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/validate/e2e/adding-key-to-config-map
History
Charles-Edouard Brétéché 2ceac72f62
chore: convert chainsaw tests to Test resource (#9113) 
* chore: convert chainsaw tests to Test resource

Signed-off-by: Charles-Edouard Brétéché <charles.edouard@nirmata.com>

* fix

Signed-off-by: Charles-Edouard Brétéché <charles.edouard@nirmata.com>

---------

Signed-off-by: Charles-Edouard Brétéché <charles.edouard@nirmata.com>
2023-12-07 22:38:30 +01:00
..
chainsaw-step-01-apply-1-1.yaml chore: convert chainsaw tests to Test resource (#9113) 2023-12-07 22:38:30 +01:00
chainsaw-step-01-apply-1-2.yaml chore: convert chainsaw tests to Test resource (#9113) 2023-12-07 22:38:30 +01:00
chainsaw-step-01-apply-1-3.yaml chore: convert chainsaw tests to Test resource (#9113) 2023-12-07 22:38:30 +01:00
chainsaw-step-01-assert-1-1.yaml chore: convert chainsaw tests to Test resource (#9113) 2023-12-07 22:38:30 +01:00
chainsaw-test.yaml chore: convert chainsaw tests to Test resource (#9113) 2023-12-07 22:38:30 +01:00
README.md chore: all chainsaw tests (#9011) 2023-11-24 11:17:58 +01:00

README.md

Description

This test validates that an existing ConfigMap can't be updated with a new key that results in violation of a policy.

Expected Behavior

The existing ConfigMap isn't patched and policy violation is reported.

Steps

Test Steps

  1. Create a Policy that denies only permits combination of two particular keys together.
  2. Create a ConfigMap that contains one of the keys.
  3. Try to patch the ConfigMap with a new key that is not permitted by the policy.
  4. Verify that the ConfigMap is not patched and policy violation is reported.
  5. Delete the Policy and ConfigMap.

Reference Issue(s)

https://github.com/kyverno/kyverno/issues/3253