only deploy patch-bond Kyverno policy if capm3 is enabled

With this MR we'll deploy Kyverno patch-bond-policy only if capm3 is used.

This Kyverno policy is very invasive (hooks on all Secrets) and result in preventing people from modifying a cluster (e.g. with an apply.sh) if Kyverno is not available, so we should only install it on the cluster if needed, ie. if capm3 is enabled.

related to #1190 (closed)

Edited by Thomas Morin

Merge request reports

Loading