node configuration about cp4d-deployment HOT 5 CLOSED

@willbranney73 Which cloud provider are you using AWS/Azure/IBM Cloud? Is it self-managed or managed openshift?

from cp4d-deployment.

@maulik-shah999 I am using Managed-openshift for IBM Cloud.

from cp4d-deployment.

Hi @willbranney73
As far as I am aware, we don't have control over which nodes to make master/worker as the ROKS cluster is installed via Ibmcloud terraform api. I will still take a look in the APIs if there is a way to achieve this.

from cp4d-deployment.

Hi @willbranney73 ,
Apologies for the delayed response.

All the nodes listed are worker nodes.

The reason why do my worker nodes have the master role?
When you run oc get nodes or oc describe node , you might see that the worker nodes have master,worker roles. In OpenShift Container Platform clusters, operators use the master role as a nodeSelector so that OCP can deploy default components that are controlled by operators, such as the internal registry, in your cluster. No master node processes, such as the API server or Kubernetes scheduler, run on your worker nodes.

For ,Red Hat OpenShift on IBM Cloud - IBM sets up the master, manages the control plane components, and automatically applies master patch updates for you. The masters are highly available and backed up automatically and you don't have access to the master nodes.

Please refer the deployment architecture below which explains the same, where the control plane(master) is IBM Managed:
https://github.com/IBM/cp4d-deployment/blob/master/managed-openshift/ibmcloud/README.md#deployment-topology

Additional docs for the same info:
https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodes (why do my worker nodes have master label)
https://cloud.ibm.com/docs/openshift?topic=openshift-cs_ov (Master nodes are IBM Managed in ROKS.

Please let me know if you have more queries

from cp4d-deployment.

Closing this issue expecting there are no more queries

from cp4d-deployment.