Home > Workload Solutions > Container Platforms > Red Hat OpenShift Container Platform > Archive > Implementation Guide—Red Hat OpenShift Container Platform 4.6 on Dell Infrastructure > Adding a remote/edge network compute node
Edge compute nodes ensure that applications run in a node that is close to the user. Before adding a remote/edge compute node:
Note: The DHCP IP address is the CSAH Primary IP address.
Note: Restart the named and haproxy services to ensure that the changes are reflected immediately.
Also ensure that:
Note: Every cluster node, including compute and control, must be able to recognize all other nodes either by its forward or reverse lookups.
The compute node is configured and rebooted automatically, as shown in the following figure.
[core@csah-pri ~]$ oc get csr | grep -i pending
csr-5jf2w 63s kubernetes.io/kube-apiserver-client-kubelet system:serviceaccount:openshift-machine-config-operator:node-bootstrapper Pending
[core@csah-pri ~]$ oc adm certificate approve csr-5jf2w
After the node-bootstrapper CSR is approved, the kuberlet CSR is displayed:
[core@csah-pri ~]$ oc get csr | grep -i pending
csr-p6c7m 11s kubernetes.io/kubelet-serving system:node:edge.demo.lab Pending
[core@csah-pri ~]$ oc adm certificate approve csr-p6c7m
[core@csah-pri ~]$ oc get nodes
NAME STATUS ROLES AGE VERSION
com-1.demo.lab Ready worker 14h v1.19.0+8d12420
com-2.demo.lab Ready worker 14h v1.19.0+2f3101c
com-3.demo.lab Ready worker 12h v1.19.0+8d12420
ctl-1.demo.lab Ready master 18h v1.19.0+8d12420
ctl-2.demo.lab Ready master 18h v1.19.0+8d12420
ctl-3.demo.lab Ready master 18h v1.19.0+8d12420
edge.demo.lab Ready worker 2m41s v1.19.0+8d12420