mirrors/kyverno
mirrors/kyverno
1
0
Fork 0
mirror of https://github.com/kyverno/kyverno.git synced 2025-04-15 08:46:36 +00:00
Code Activity
kyverno/test/conformance/chainsaw/globalcontext/not-ready
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
clusterpolicy-failed.yaml feat: enhance global context (#9710) 2024-02-23 10:34:04 +00:00
clusterpolicy-ready.yaml feat: enhance global context (#9710) 2024-02-23 10:34:04 +00:00
clusterpolicy.yaml chore: rename validationFailureAction to failureAction under the rule (#10893) 2024-08-27 20:07:57 +00:00
gctxentry.yaml feat(gctx): retry logic (#10796) 2024-08-21 19:32:58 +00:00
main-deployment.yaml feat(gctx): retry logic (#10796) 2024-08-21 19:32:58 +00:00
namespace.yaml feat: enhance global context (#9710) 2024-02-23 10:34:04 +00:00
new-deployment-exists.yaml feat: enhance global context (#9710) 2024-02-23 10:34:04 +00:00
new-deployment.yaml feat(gctx): retry logic (#10796) 2024-08-21 19:32:58 +00:00
README.md feat: enhance global context (#9710) 2024-02-23 10:34:04 +00:00

README.md

Description

This test verifies that the policy becomes not ready if the referenced Global Context Entries don't exist anymore.

Expected Behavior

new-deployment should not be created because the policy is not ready.

Reference Issues