kcm pod crashloops because port is already in use. I saw a case with cluster-policy-manager container but it's not limited to it. Crashlooping triggers alerts and adds backoff for the pod so it start slower. Container can be restarted while the pods stays. For that reason, we need to check the port availability in the same process as we listen, not in an init container which isn't re-run.
*** Bug 1853889 has been marked as a duplicate of this bug. ***
This is breaking oVirt, as stated on https://bugzilla.redhat.com/show_bug.cgi?id=1853889
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196