Matthias Weilinger bb3e7d9ddc add allowExistingViolations option in policy chart (#11656) ... Until now it was not possible to set the allowExistingViolations for predefined policies in the policies chart. By default it should be set to , identical to how it is set up in the CRDs. Not only does this now allow users to set the config according to their needs, but this also solves a problem with ArgoCD. As the CRDs set it to true, but the template does not specifically declare the field, ArgoCD falls into a constant sync loop of trying to remove the field. Signed-off-by: ProbstenHias <matthias.weilinger@gmx.de> Co-authored-by: Vishal Choudhary <vishal.choudhary@nirmata.com>		2024-12-02 09:20:26 +05:30
..
custom-policies.yaml	feat: ability to add custom policies in values file (#10320)	2024-05-29 16:24:36 +00:00
require-non-root-groups.yaml	add allowExistingViolations option in policy chart (#11656)	2024-12-02 09:20:26 +05:30