Proposed title of this feature request
A: Custom node naming when openshift scales and upgrades
What is the nature and description of the request?
A: During the automated scale-up and rollout of new open shift nodes, OCP should respect a naming convention provided by cluster admins.
Why would you like this alteration? (List the business requirements here)
A: In order to be compliant with the security, reporting, auditing, and other requirements, nodes should follow a predictable naming convention. EX: alfropenshiftnode01, boavopenshiftnode02, etc..
How would you like to achieve this? (List the functional requirements here)
A: Can be via configmap or other cluster configuration on how nodes naming are generated