How to recover from Node crashing due to incorrect KubeletConfig?

Issue

NOTE: This solution requires SSH access to the OpenShift Nodes. If you do not have access to the SSH credentials or are unable to access the Nodes via SSH for another reason, such as network limitations, this solution should NOT be used and the Nodes must be replaced with a new Node.

After configuring values using the KubeletConfig object, Nodes in the cluster have restarted but are still in the NotReady state and have remained in this state for over 30 minutes.

$ oc get nodes 

NAME        STATUS                        ROLES     AGE   VERSION
op1         NotReady,SchedulingDisabled   worker    35d   v1.27.14+95b99ee