-
Feature Request
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
False
-
None
-
False
-
Not Selected
-
-
-
-
-
- Proposed title of this feature request
Ability to assign a customized control plane machine name by the CPMS CR
2. What is the nature and description of the request?
Customer requires to apply customized nomenclature for the nodes.
For workers it is applied as per machineset name but for control plane, in case of having CPMS CR as active mode, the control plane machine inherit the name of the cluster:
$ oc get controlplanemachinesets.machine.openshift.io NAME DESIRED CURRENT READY UPDATED UNAVAILABLE STATE AGE cluster 3 3 3 3 Active 83m $ oc get controlplanemachinesets.machine.openshift.io cluster -o json | jq .spec.selector.matchLabels { "machine.openshift.io/cluster-api-cluster": "ci-ln-87m0grk-1d09d-wgstj", "machine.openshift.io/cluster-api-machine-role": "master", "machine.openshift.io/cluster-api-machine-type": "master" } $ oc get machine | grep master ci-ln-87m0grk-1d09d-wgstj-master-0 Running Standard_D8s_v3 eastus 3 83m ci-ln-87m0grk-1d09d-wgstj-master-1 Running Standard_D8s_v3 eastus 2 83m ci-ln-87m0grk-1d09d-wgstj-master-2 Running Standard_D8s_v3 eastus 1 83m $ oc get nodes | grep master ci-ln-87m0grk-1d09d-wgstj-master-0 Ready control-plane,master 78m v1.27.6+f67aeb3 ci-ln-87m0grk-1d09d-wgstj-master-1 Ready control-plane,master 78m v1.27.6+f67aeb3 ci-ln-87m0grk-1d09d-wgstj-master-2 Ready control-plane,master 77m v1.27.6+f67aeb3
3. Why does the customer need this? (List the business requirements here)
Due to the organization compliance needs, it’s required to give specific nomenclature to the nodes.
Customer has a big fleet of clusters and is working on their strategy for OCP 4.14 new installations
4. List any affected packages or components.
Control Plane Machine Set
- depends on
-
OCPSTRAT-1418 Allow Custom machine names when using the CPMS feature
- In Progress