Description of problem:
On a specific big cluster (~500 nodes) kubemacpool-mac-controller-manager pod never reaches Ready state, making it impossible to define VMs.

Version-Release number of selected component (if applicable):
CNV-4.9.1
$ oc version
Client Version: 4.9.12
Server Version: 4.9.12
Kubernetes Version: v1.22.3+e790d7f

How reproducible:
repeatedly, on one specific cluster

Steps to Reproduce:
1. Install OpenShift Virtualization

Actual results:

$ oc get pod -n openshift-cnv -l app=kubemacpool
NAME READY STATUS RESTARTS AGE
kubemacpool-cert-manager-7b7bcfc9db-2c8p6 1/1 Running 0 3h13m
kubemacpool-mac-controller-manager-88b9c5b99-tt4tk 0/1 Running 33 (112s ago) 5h27m

$ ./vm.sh |oc apply -f -
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "mutatevirtualmachines.kubemacpool.io": failed to call webhook: Post "https://kubemacpool-service.openshift-cnv.svc:443/mutate-virtualmachines?timeout=10s": dial tcp 10.129.0.72:8000: connect: connection refused

Expected results:
kubemacpool is READY, serving unique MAC addresses to VMs. VM is defined.

Additional info:
Use
$ oc label namespace mynamespace mutatevirtualmachines.kubemacpool.io=ignore
to disable kubemacpool in your namespace. Make sure that your VMs do not refer to kubemacpool.io in their finalizers.