Add GenerateExisting option for clone-config
currently clone-config policy only works on new resources and skips and existing resources
adding spec.generateExisting: true ensures that any resources added before this policy starts, while this policy is paused, or if kyverno restarts, still get the cloned config
Edited by Jeff Davis