Kubernetes : Add Worker Nodes2026/08/10 |
|
Add new Worker Nodes to existing Kubernetes Cluster.
This example is based on the cluster environment like follows.
+----------------------+ +----------------------+
| [ ctrl.srv.world ] | | [ dlp.srv.world ] |
| Manager Node | | Control Plane |
+-----------+----------+ +-----------+----------+
eth0|10.0.0.25 eth0|10.0.0.30
| |
------------+--------------------------+-----------
| |
eth0|10.0.0.51 eth0|10.0.0.52
+-----------+----------+ +-----------+----------+
| [ node01.srv.world ] | | [ node02.srv.world ] |
| Worker Node#1 | | Worker Node#2 |
+----------------------+ +----------------------+
|
| [1] |
On a new Node, Configure common settings to join in Cluster, refer to here. |
| [2] | Confirm join command on Control Plane Node. |
|
[root@dlp ~]# kubeadm token create --print-join-command kubeadm join 10.0.0.25:6443 --token se1xas.k2mu4hk4gsu7wven --discovery-token-ca-cert-hash sha256:ac6990d8007cb72c8c1ea1105ddffbb3d9905e425309e8dd5a14f367771fb7d7 |
| [3] | Run join command on a new Node. |
|
[root@node03 ~]# kubeadm join 10.0.0.25:6443 --token g0ifzw.bd840i4jchlgkw23 \ --discovery-token-ca-cert-hash sha256:a750982d5929a1ec15fe1236f72b066d5a84d0875441f5797631373c9f5602f0 [preflight] Running pre-flight checks [preflight] Reading configuration from the "kubeadm-config" ConfigMap in namespace "kube-system"... [preflight] Use 'kubeadm init phase upload-config kubeadm --config your-config-file' to re-upload it. [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/instance-config.yaml" [patches] Applied patch of type "application/strategic-merge-patch+json" to target "kubeletconfiguration" [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml" [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env" [kubelet-start] Starting the kubelet [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s [ 142.272840] Warning: Unmaintained driver is detected: nft_compat [ 142.274014] Warning: Unmaintained driver is detected: nft_compat_module_init [kubelet-check] The kubelet is healthy after 501.109842ms [kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap This node has joined the cluster: * Certificate signing request was sent to apiserver and a response was received. * The Kubelet was informed of the new secure connection details. Run 'kubectl get nodes' on the control-plane to see this node join the cluster. |
| [4] | Verify settings on Manager Node. That's OK if the status of new Node turns to [STATUS = Ready]. |
|
[root@ctrl ~]# kubectl get nodes NAME STATUS ROLES AGE VERSION dlp-1.srv.world Ready control-plane 10m v1.36.3 dlp.srv.world Ready control-plane 2d23h v1.36.3 node01.srv.world Ready <none> 2d23h v1.36.3 node02.srv.world Ready <none> 2d23h v1.36.3 node03.srv.world Ready <none> 48s v1.36.3[root@ctrl ~]# kubectl get pods -A -o wide | grep node03 calico-system calico-node-zjshp 1/1 Running 0 63s 10.0.0.53 node03.srv.world <none> <none> calico-system calico-typha-7bf9667c4d-mj22m 1/1 Running 0 56s 10.0.0.53 node03.srv.world <none> <none> calico-system csi-node-driver-dqr4q 2/2 Running 0 63s 10.85.0.2 node03.srv.world <none> <none> kube-system kube-proxy-gpdzn 1/1 Running 0 63s 10.0.0.53 node03.srv.world <none> <none> |
| Sponsored Link |