Description of problem:

In the 'Pausing a MachineHealthCheck resource' upgrade procedure, the default MHC, machine-api-termination-handler, does not need to be stopped

https://docs.openshift.com/container-platform/4.17/updating/updating_a_cluster/updating-cluster-cli.html#machine-health-checks-pausing_updating-cluster-cli

This procedure is saying:

To avoid rebooting such nodes, pause all the MachineHealthCheck resources before updating the cluster.

However some clusters have the MachineHealthCheck/machine-api-termination-handler as default. This MHC does not deploy new node if the node is notReady. As such, the documentation should explicitly note that machine-api-termination-handler is an exception and does not need to be paused during the upgrade process."