Update Webhook Configuration objects when Reconciling

[pliurh]

Sync content of MutatingWebhookConfiguration and ValidatingWebhookConfiguration
CRs when needed.

https://bugzilla.redhat.com/show_bug.cgi?id=1969761

[zshi-redhat]

@pliurh could you explain how this PR can fix the issue of admission-controller API upgrade from v1beta to v1?

[pliurh]

@pliurh could you explain how this PR can fix the issue of admission-controller API upgrade from v1beta to v1?

The root cause is not the mismatch of the API version itself, since kube-apiserver can handle the version conversion automatically. It is because, in functions syncMutatingWebhook and syncValidatingWebhook, there is no content sync logic for the webhook config CR if it already exists. The field admissionReviewVersions in the CRs are not updated.

sriov-network-operator/bindata/manifests/operator-webhook/003-webhook.yaml

Line 16 in fc360d9

admissionReviewVersions: [v1]

With this patch, all the objects follow the same sync logic. So the issue can be fixed.

[zshi-redhat]

/lgtm

[pliurh]

@jcaamano PTAL.

I don't think we need to keep the caBundle when syncing the webhook config as you proposed in #115 since it can always be reinjected by either cert-manger or the openshift-service-ca-operator.