Closed kohend closed 6 months ago
Please tell us your actual Kyverno and Kubernetes versions used.
Edited to specify exact versions
Have you installed Kyverno into the Namespace named system
?
Yes
That is why the policy does not work. Kyverno excludes its own Namespace by default as mentioned in the documentation, so therefore it does not "see" modifications to a Secret also located in that same Namespace. Kyverno should not be installed in a Namespace co-located with other components. It should be installed in its own Namespace. The subjects of policies may not be in Kyverno's Namespace regardless of the type of rule.
Thank you, as I was not the one that installed the cluster, I didn't think of checking that.
Kyverno Version
1.10.1
Kubernetes Version
1.25.4
Kubernetes Platform
Other (specify in description)
Description
I'm trying to sync the cert-manager created tls certificate using kyverno, I may have made the wrong policy, but it seems consistent with the docs. It doesn't sync or even behaves as if there's anything to sync. Running on OCI (OKE)
Steps to reproduce
Expected behavior
That when the secret is updated, it'll sync that secret
Screenshots
No response
Kyverno logs
Slack discussion
No response
Troubleshooting