Customers trying to UPI Install a OCP Cluster with a Standalone ESX Server face openshift-machine-api restarts periodically.

Engineering reviewing the error that it was returning and the explanation is:

* a standalone host is only a ComputeResource
* Only a cluster can be casted from ComputeResource to ClusterComputeResource

Then, it's expecting to find a cluster, not a ComputeResource. 

1.
2.
3.

 oc get po
NAME                                           READY   STATUS    RESTARTS        AGE
cluster-autoscaler-operator-59976488c7-q6l7x   2/2     Running   0               160m
cluster-baremetal-operator-8647776fdc-xwzg7    2/2     Running   0               160m
machine-api-controllers-5b5ff45b9b-22wrd       7/7     Running   17 (7m6s ago)   111m
machine-api-operator-9b68df68c-rqlcn           2/2     Running   0               111m

oc describe po machine-api-controllers-5b5ff45b9b-22wrd
...
Events:
  Type     Reason          Age   From               Message
  ----     ------          ----  ----               -------
  Normal   Scheduled       114m  default-scheduler  Successfully assigned openshift-machine-api/machine-api-controllers-5b5ff45b9b-22wrd to dreecaas0003.pka.bankenit.de
  Normal   AddedInterface  114m  multus             Add eth0 [100.64.0.33/24] from openshift-sdn
  Normal   Pulled          114m  kubelet            Container image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:130fd32e81a950283e4ac7963f35e7e104864ebc439784ff0d2855d639b9d211" already present on machine
  Normal   Created         114m  kubelet            Created container machineset-controller
  Normal   Started         114m  kubelet            Started container machineset-controller
  Normal   Pulled          114m  kubelet            Container image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:eb4689ba4b82e603bcd43ecddb2ad492358e1eb8cc773b52674684ef25d05eaa" already present on machine
  Normal   Created         114m  kubelet            Created container machine-controller
  Normal   Started         114m  kubelet            Started container machine-controller
  Normal   Pulled          114m  kubelet            Container image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:130fd32e81a950283e4ac7963f35e7e104864ebc439784ff0d2855d639b9d211" already present on machine
  Normal   Created         114m  kubelet            Created container nodelink-controller
  Normal   Started         114m  kubelet            Started container nodelink-controller
  Normal   Pulled          114m  kubelet            Container image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:130fd32e81a950283e4ac7963f35e7e104864ebc439784ff0d2855d639b9d211" already present on machine
  Normal   Created         114m  kubelet            Created container machine-healthcheck-controller
  Normal   Started         114m  kubelet            Started container machine-healthcheck-controller
  Normal   Started         114m  kubelet            Started container kube-rbac-proxy-mhc-mtrc
  Normal   Created         114m  kubelet            Created container kube-rbac-proxy-machineset-mtrc
  Normal   Started         114m  kubelet            Started container kube-rbac-proxy-machineset-mtrc
  Normal   Pulled          114m  kubelet            Container image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:eb4689ba4b82e603bcd43ecddb2ad492358e1eb8cc773b52674684ef25d05eaa" already present on machine
  Normal   Created         114m  kubelet            Created container kube-rbac-proxy-machine-mtrc
  Normal   Started         114m  kubelet            Started container kube-rbac-proxy-machine-mtrc
  Normal   Pulled          114m  kubelet            Container image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:eb4689ba4b82e603bcd43ecddb2ad492358e1eb8cc773b52674684ef25d05eaa" already present on machine
  Normal   Created         114m  kubelet            Created container kube-rbac-proxy-mhc-mtrc
  Warning  ProbeError      114m  kubelet            Readiness probe error: Get "http://100.64.0.33:9442/healthz": dial tcp 100.64.0.33:9442: connect: connection refused
body:
  Warning  Unhealthy   114m  kubelet  Readiness probe failed: Get "http://100.64.0.33:9442/healthz": dial tcp 100.64.0.33:9442: connect: connection refused
  Warning  ProbeError  114m  kubelet  Readiness probe error: Get "http://100.64.0.33:9440/healthz": dial tcp 100.64.0.33:9440: connect: connection refused
body:
  Warning  ProbeError  114m  kubelet  Readiness probe error: Get "http://100.64.0.33:9441/healthz": dial tcp 100.64.0.33:9441: connect: connection refused
body:
  Normal   Pulled   44m (x13 over 114m)   kubelet  Container image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:130fd32e81a950283e4ac7963f35e7e104864ebc439784ff0d2855d639b9d211" already present on machine
  Warning  BackOff  56s (x311 over 108m)  kubelet  Back-off restarting failed container


oc logs machine-api-controllers-5b5ff45b9b-22wrd kube-rbac-proxy-machine-mtrc
I1018 08:22:19.711659       1 main.go:151] Reading config file: /etc/kube-rbac-proxy/config-file.yaml
I1018 08:22:19.713776       1 main.go:181] Valid token audiences:
I1018 08:22:19.713822       1 main.go:305] Reading certificate files
I1018 08:22:19.714331       1 main.go:339] Starting TCP socket on 0.0.0.0:8441
I1018 08:22:19.714606       1 main.go:346] Listening securely on 0.0.0.0:8441
2022/10/18 08:28:16 http: proxy error: dial tcp [::1]:8081: connect: connection refused
2022/10/18 08:31:00 http: proxy error: dial tcp [::1]:8081: connect: connection refused
2022/10/18 08:31:16 http: proxy error: dial tcp [::1]:8081: connect: connection refused
2022/10/18 08:31:30 http: proxy error: dial tcp [::1]:8081: connect: connection refused