Ubuntu 22.04
Sponsored Link

Kubernetes : ノードを削除する
2022/11/03
 
既存の Kubernetes クラスターからノードを削除する場合は以下のように設定します。
以下のように 4 台のノードで構成している Kubernetes クラスターから [snode03.srv.world] ノードを削除します。
-----------+---------------------------+--------------------------+--------------+
           |                           |                          |              |
       eth0|10.0.0.25              eth0|10.0.0.71             eth0|10.0.0.72     |
+----------+-----------+   +-----------+-----------+   +-----------+-----------+ |
|  [ ctrl.srv.world ]  |   |  [snode01.srv.world]  |   |  [snode02.srv.world]  | |
|     Control Plane    |   |      Worker Node      |   |      Worker Node      | |
+----------------------+   +-----------------------+   +-----------------------+ |
                                                                                 |
------------+--------------------------------------------------------------------+
            |
        eth0|10.0.0.73
+-----------+-----------+
|  [snode03.srv.world]  |
|      Worker Node      |
+-----------------------+

[1] Master ノードで対象ノードを削除します。
# 対象ノードを安全に削除するための事前準備
# --ignore-daemonsets ⇒ DeamonSet の Pod は無視
# --delete-emptydir-data ⇒ emptyDir ボリュームを持つ Pod は無視
# --force ⇒ 単体で作成された Pod も削除

root@ctrl:~#
kubectl drain snode03.srv.world --ignore-daemonsets --delete-emptydir-data --force

Warning: ignoring DaemonSet-managed Pods: kube-system/calico-node-762x8, kube-system/kube-proxy-lm25n
node/snode03.srv.world drained

# 一定時間経過後に確認
# 時間は環境によって異なる

root@ctrl:~#
kubectl get nodes snode03.srv.world

NAME                STATUS                     ROLES    AGE   VERSION
snode03.srv.world   Ready,SchedulingDisabled   <none>   14m   v1.25.3

# 削除処理を実行

root@ctrl:~#
kubectl delete node snode03.srv.world

node "snode03.srv.world" deleted

root@ctrl:~#
kubectl get nodes

NAME                STATUS   ROLES           AGE   VERSION
ctrl.srv.world      Ready    control-plane   26h   v1.25.3
snode01.srv.world   Ready    <none>          25h   v1.25.3
snode02.srv.world   Ready    <none>          25h   v1.25.3
[2] 削除したノードで、kubeadm の設定をリセットしておきます。
root@snode03:~#
kubeadm reset

[reset] WARNING: Changes made to this host by 'kubeadm init' or 'kubeadm join' will be reverted.
[reset] Are you sure you want to proceed? [y/N]: y
W1103 04:37:53.839439    7438 removeetcdmember.go:85] [reset] No kubeadm config, using etcd pod spec to get data directory
[reset] No etcd config found. Assuming external etcd
[reset] Please, manually reset etcd to prevent further issues
[reset] Stopping the kubelet service
[reset] Unmounting mounted directories in "/var/lib/kubelet"
[reset] Deleting contents of directories: [/etc/kubernetes/manifests /etc/kubernetes/pki]
[reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf]
[reset] Deleting contents of stateful directories: [/var/lib/kubelet]

The reset process does not clean CNI configuration. To do so, you must remove /etc/cni/net.d

The reset process does not reset or clean up iptables rules or IPVS tables.
If you wish to reset iptables, you must do so manually by using the "iptables" command.

If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar)
to reset your system's IPVS tables.

The reset process does not clean your kubeconfig files and you must remove them manually.
Please, check the contents of the $HOME/.kube/config file.
関連コンテンツ