Gatekeeper version: 3.15.1 (Gatekeeper Operator from REDHAT)
Openshift version: 4.14
The following yaml doesn't seem to do the job, its supposed to trigger deployment rollout when an annotation is modified.
I could ofcourse have used a controller here such as wave or reloader or kyverno to accomplish this, but it would have been really preferable to use Gatekeeper as we also use it for other stuff.
The secret and the deployment, both have the same labels on them, both are on the same namespace, so I kind of expected that Gatekeeper would listen for secret changes and annotate the deployment to trigger a restart.
Environment:
The following yaml doesn't seem to do the job, its supposed to trigger deployment rollout when an annotation is modified. I could ofcourse have used a controller here such as wave or reloader or kyverno to accomplish this, but it would have been really preferable to use Gatekeeper as we also use it for other stuff.
The secret and the deployment, both have the same labels on them, both are on the same namespace, so I kind of expected that Gatekeeper would listen for secret changes and annotate the deployment to trigger a restart.
Secret:
Deployment: I tried to put the label under metadata, but that did not make any difference.
Gatekeeper's mutatingwebhookconfiguration by default is set to make changes for CREATE and UPDATE operation: