Closed ugur99 closed 1 year ago
@ugur99 how are you trying to change the name? Are you using the flag? mutating-webhook-configuration-name
Hi @acpana thank you for the quick reply, we're using helm chart in order to deploy and upgrade the gatekeeper. And related variable in the helm chart is mutatingWebhookName
@acpana I think we found the problem, since the gatekeeper-controller-manager manifest is missing the appropriate flags, it uses the default values of these variables. This PR should fix the problem.
What steps did you take and what happened: We are trying to deploy opa-gatekeeper with a different
mutatingWebhookName
rather than the default one, but it is not working properly. The same problem occurs when upgrading the existing 'opa-gatekeeper' deployment. The logs are as follows:Using the default value solves the problem. Could it be hard-coded somewhere in the code?
What did you expect to happen:
mutatingWebhookName
should be able to be manipulated for new and existing deployments.Anything else you would like to add: Mutating webhooks are called in lexical order, and since we want to use opa-gatekeeper as the last mutator; we need to manipulate its mutationing webhook resource name something like
zzz-gatekeeper-mutating-webhook-configuration
.Environment:
kubectl version
):1.24.10