kubemacpool restarts with error when kubevirt is installed after kubemacpool manager starts

[RamLavi]

Scenario:
kubemacpool is deployed when kubevirt CRD is not yet deployed.
Then kubevirt is installed.

What happens: kubemacpool pod restarts with an error:

controller with name mac-range-configmap already exists. Controller names must be unique to avoid multiple controllers reporting the same metric.

[RamLavi]

I think it's OK that kubmeacpool restarts, it just doesn't need to be with this error.

[RamLavi]

Upon checking, it seems like controller-runtime is "remembering" the controller even though the manager is reset (see here where they use static set)