+++ This bug was initially created as a clone of Bug #1968336 +++

Description of problem:

It's impossible to know what is the host role (master or worker) when installing a multi-node cluster with the operator.

I think it's also required to set the bootstrap flag on the agent CR as well

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Install a multi-node cluster 
2.
3.

Actual results:
Try to figure out the role of each host

Expected results:
See have a hostRole field on the agent 
See if the host is the bootstrap node

Additional info:

--- Additional comment from frolland on 20210607T09:05:11

@mfilanov FYI

--- Additional comment from mfilanov on 20210607T09:09:34

Originally auto assigned role should not be supported in kube-api but we cannot require it on creation because

--- Additional comment from mfilanov on 20210607T09:14:02


Originally auto assigned role should not be supported in kube-api but we cannot require it on creation because the CR is created automatically. 
User can set the role in two ways, bmac annotations, edit the spec of the agent. 
possible solution is to add the role to the status then even auto-assign will be selected once the installation is starting. 
Another way is to add a condition in the agent, but then cluster deployment controller will need to validate those conditions before starting the installation. 

@atraeger what do you think? 


Bootstrap can be added to the status (probably should be a different ticket)

--- Additional comment from frolland on 20210610T08:03:27

Also HostNTPSources should be added.