Description:
The customer would like the ability to rename the controlPlane.name field in the install-config.yaml.
Currently, it defaults to master, and this value is referenced internally by components like the MachineConfigPool and other control plane-related resources.
As OpenShift itself is moving away from the “master” terminology in favor of “control-plane”, the customer would also like to follow the same naming convention. However, modifying the field from master to control-plane is not currently supported and leads to reconciliation issues in the cluster.

Reason / Business Impact:
The customer wants to align with inclusive and updated OpenShift naming conventions.

It helps maintain consistent terminology across their infrastructure.

The current restriction makes it difficult to adopt the newer naming standard.

Request:
Please add support for customizing the controlPlane.name field in the install-config.yaml so users can use names like control-plane without breaking MachineConfigPool or other control plane resource references.