02-Node and Cluster
文章目录
学习参考:Node
查看节点
bash
# 查看节点清单
root@master30:~# kubectl get nodes
NAME STATUS ROLES AGE VERSION
master30.xiaoma.cloud Ready control-plane 21d v1.30.2
worker31.xiaoma.cloud Ready <none> 21d v1.30.2
worker32.xiaoma.cloud Ready <none> 21d v1.30.2
# 查看特定节点详细信息
root@master30:~# kubectl describe node worker31.xiaoma.cloud
删除节点
以 worker31 节点为例。
bash
# 设置节点为维护模式
root@master30:~# kubectl drain worker31.xiaoma.cloud --ignore-daemonsets
node/worker31.xiaoma.cloud cordoned
Warning: ignoring DaemonSet-managed Pods: kube-system/calico-node-v8jdn, kube-
system/kube-proxy-27vl2
evicting pod kube-system/calico-kube-controllers-7cb4fd5784-jx2xl
pod/calico-kube-controllers-7cb4fd5784-jx2xl evicted
node/worker31.xiaoma.cloud drained
root@master30:~# kubectl get nodes
NAME STATUS ROLES AGE VERSION
master30.xiaoma.cloud Ready control-plane 41h v1.30.2
worker31.xiaoma.cloud Ready,SchedulingDisabled <none> 41h v1.30.2
worker32.xiaoma.cloud Ready <none> 41h v1.30.2
# 删除 worker31 节点
root@master30:~# kubectl delete node worker31.xiaoma.cloud
node"worker31.xiaoma.cloud" deleted
root@master30:~# kubectl get nodes
NAME STATUS ROLES AGE VERSION
master30.xiaoma.cloud Ready control-plane 41h v1.30.2
worker32.xiaoma.cloud Ready <none> 41h v1.30.2
# 重置删除的 worker31 节点
root@worker31:~# kubeadm reset -f
[preflight] Running pre-flight checks
W1019 07:37:44.242023 7660 removeetcdmember.go:106] [reset] No kubeadm config,
using etcd pod spec to get data directory
[reset] Deleted contents of the etcd data directory: /var/lib/etcd
[reset] Stopping the kubelet service
[reset] Unmounting mounted directories in"/var/lib/kubelet"
[reset] Deleting contents of directories: [/etc/kubernetes/manifests
/var/lib/kubelet /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]
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.
删除集群
删除集群流程:
-
- 删除所有 node
-
- 删除所有 master
具体步骤:
- 删除所有 master
-
- 删除所有node节点
bash
root@master30:~# kubectl drain worker31.xiaoma.cloud --ignore-daemonsets --force
root@master30:~# kubectl drain worker32.xiaoma.cloud --ignore-daemonsets --force
root@master30:~# kubectl delete node worker31.xiaoma.cloud worker32.xiaoma.cloud
# 重置节点,注意执行位置
root@worker31:~# kubeadm reset -f
root@worker32:~# kubeadm reset -f
-
- 删除master节点
bash
# 删除集群前获取集群配置
root@master30:~# kubectl get cm kubeadm-config -n kube-system -o yaml >
kubeadm.yml
# 修改kubeadm.yml内容如下:
root@master30:~# vim kubeadm.yml
# 先删除22-28行,后删除1-3行,效果如下
apiServer:
timeoutForControlPlane: 4m0s
apiVersion: kubeadm.k8s.io/v1beta3
certificatesDir: /etc/kubernetes/pki
clusterName: kubernetes
controllerManager: {}
dns: {}
etcd:
local:
dataDir: /var/lib/etcd
imageRepository: hub.xiaoma.cloud/kubernetes
kind: ClusterConfiguration
kubernetesVersion: v1.30.2
networking:
dnsDomain: cluster.local
podSubnet: 10.224.0.0/16
serviceSubnet: 10.96.0.0/12
scheduler: {}
root@master30:~# kubectl delete node master30.xiaoma.cloud
root@master30:~# kubeadm reset -f
root@master30:~# rm -fr .kube/
重建集群
bash
# 初始化集群
root@master30:~# kubeadm init --config kubeadm.yml
# 也可以使用之前的命令
root@master30:~# kubeadm init --kubernetes-version=v1.30.2 --pod-network-
cidr=10.224.0.0/16 --image-repository hub.xiaoma.cloud/kubernetes
# 配置凭据
root@master30:~# mkdir -p $HOME/.kube
root@master30:~# sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
root@master30:~# sudo chown $(id -u):$(id -g) $HOME/.kube/config
# 配置网络
root@master30:~# kubectl apply -f calico.yaml
# 加入集群
root@worker31:~# kubeadm join 10.1.8.30:6443 --token ky95b9.sjg0fn21pdi1m0xz -
-discovery-token-ca-cert-hash sha256xxxxxxx