1. Proposed title of this feature request

-> Support for scheduling metal3 pod with provisioning interface enabled on a single master node

2. What is the nature and description of the request?

-> In baremetal environment with provisioning network enabled, the metal3 pod gets scheduled on the master node holding the provisioning IP. In environments where the provisioning ip cannot be moved to other master nodes, the metal3 pod has to be manually restarted multiple times to schedule it on the specific master node. 

3. Why does the customer need this? (List the business requirements here)

-> In baremetal environments with provisioning network enabled, a provisioning interface is required on all the master nodes for the provisioning Ip to move to next master. Or a MAC address of an interface is required to be provided. 

If cases where the provisioningIP cannot be moved to other masters and baremetal provisioning is required to happen from one master, there is no supported way to achieve this currently.

4. List any affected packages or components.

• BareMetal Operator
• Provisioning Resource
• Metal3 pod