1. Proposed title of this feature request
Support to add worker nodes into the BareMetal OCP cluster provisioned by ABI with BMH and machine resources populated for the new added node.

2. What is the nature and description of the request?
After the BareMetal OCP cluster is provisioned by ABI(https://docs.openshift.com/container-platform/4.17/installing/installing_with_agent_based_installer/installing-with-agent-based-installer.html), there will be the BMH and Machine resource generated for the nodes in the cluster so that the user can check the hardware and software status via those resources. But then if we follow the Red Hat formal document to add a new worker node into the OCP cluster(https://docs.openshift.com/container-platform/4.17/nodes/nodes/nodes-nodes-adding-node-iso.html), there won't be any BMH and Machine resources generated for the new node which will confuse the user for such kind of inconsistency and also user can't check the hardware and software status via BMH after the node added into the OCP cluster. 
This request is about to make the consistency for the nodes in the OCP cluster no matter the node is provisioned into the cluster by ABI or is added into the cluster after the provision with ABI.

3. Why does the customer need this? (List the business requirements here)
Keep the  info of all nodes in the BareMetal OCP cluster consistent with BMH and machine resources so that user can check the hardware and software info of the node via BMH no matter the node is provisioned into OCP cluster by ABI or is added into the cluster after the provisioning with ABI.

4. List any affected packages or components.
BMH