Role terminology confusion when creating a Node from MetalK8s UI

[thomasdanan]

When looking at a Node from CLI (kubectl get node <name>) or from the UI we can get the Node roles:

When we create a Node from MetalK8s UI, the user is asked to choose between 3 roles:

However, those roles are not the node roles and it confuses the user:

Roles/Workload Plane: enable any workload applications run on this Node
Roles/Control Plane: enable master and etcd services run on this Node
Roles/Infra: enable infra services run on this Node

Don't you think it would make more sense to use a different label or directly use the description above?

[NicolasT]

Internally we have the 4 distinct roles (and according labels, taints, what gets deployed/bound where,...), and we should stick to those. We decided not to expose all 4 of them in the UI and instead bundle etcd and master up into Control Plane to simplify things for a UI user: in general you'll want to have etcd and master (which we should likely rename as well) colocated, but we still have the option not to.