获取节点名
# kubectl get nodes -A
NAME STATUS ROLES AGE VERSION
tmp-server1 Ready control-plane,master 13m v1.20.1
首先查看master节点污点策略
其中Taints的值为node-role.kubernetes.io/master:NoSchedule
Taints: node-role.kubernetes.io/master:NoSchedule
# kubectl describe nodes tmp-server1
Name: tmp-server1
Roles: control-plane,master
Labels: beta.kubernetes.io/arch=amd64
beta.kubernetes.io/os=linux
kubernetes.io/arch=amd64
kubernetes.io/hostname=tmp-server1
kubernetes.io/os=linux
node-role.kubernetes.io/control-plane=
node-role.kubernetes.io/master=
Annotations: kubeadm.alpha.kubernetes.io/cri-socket: /var/run/dockershim.sock
node.alpha.kubernetes.io/ttl: 0
projectcalico.org/IPv4Address: 66.42.45.144/23
projectcalico.org/IPv4IPIPTunnelAddr: 10.244.62.192
volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp: Wed, 26 Mar 2025 13:48:01 +0000
Taints: node-role.kubernetes.io/master:NoSchedule
Unschedulable: false
Lease:
HolderIdentity: tmp-server1
AcquireTime: <unset>
RenewTime: Wed, 26 Mar 2025 14:02:16 +0000
Conditions:
Type Status LastHeartbeatTime LastTransitionTime Reason Message
---- ------ ----------------- ------------------ ------ -------
NetworkUnavailable False Wed, 26 Mar 2025 13:48:35 +0000 Wed, 26 Mar 2025 13:48:35 +0000 CalicoIsUp Calico is running on this node
MemoryPressure False Wed, 26 Mar 2025 13:59:08 +0000 Wed, 26 Mar 2025 13:47:58 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available
DiskPressure False Wed, 26 Mar 2025 13:59:08 +0000 Wed, 26 Mar 2025 13:47:58 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure
PIDPressure False Wed, 26 Mar 2025 13:59:08 +0000 Wed, 26 Mar 2025 13:47:58 +0000 KubeletHasSufficientPID kubelet has sufficient PID available
Ready True Wed, 26 Mar 2025 13:59:08 +0000 Wed, 26 Mar 2025 13:48:26 +0000 KubeletReady kubelet is posting ready status. AppArmor enabled
Addresses:
InternalIP: 66.42.45.144
Hostname: tmp-server1
Capacity:
cpu: 4
ephemeral-storage: 156742152Ki
hugepages-1Gi: 0
hugepages-2Mi: 0
memory: 8121900Ki
pods: 110
Allocatable:
cpu: 4
ephemeral-storage: 144453567045
hugepages-1Gi: 0
hugepages-2Mi: 0
memory: 8019500Ki
pods: 110
System Info:
Machine ID: b9f1b18ba6ab4aa6801b75e04aa42154
System UUID: 7848a792-70cb-46f3-a46e-a93e76ea13c1
Boot ID: ddef4732-7364-439f-9594-7497ca028cd1
Kernel Version: 5.15.0-134-generic
OS Image: Ubuntu 22.04.5 LTS
Operating System: linux
Architecture: amd64
Container Runtime Version: docker://26.1.3
Kubelet Version: v1.20.1
Kube-Proxy Version: v1.20.1
PodCIDR: 10.244.0.0/24
PodCIDRs: 10.244.0.0/24
Non-terminated Pods: (9 in total)
Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits AGE
--------- ---- ------------ ---------- --------------- ------------- ---
kube-system calico-kube-controllers-577f77cb5c-ndjx2 0 (0%) 0 (0%) 0 (0%) 0 (0%) 14m
kube-system calico-node-s898h 250m (6%) 0 (0%) 0 (0%) 0 (0%) 14m
kube-system coredns-7f89b7bc75-clvm8 100m (2%) 0 (0%) 70Mi (0%) 170Mi (2%) 14m
kube-system coredns-7f89b7bc75-l4pp9 100m (2%) 0 (0%) 70Mi (0%) 170Mi (2%) 14m
kube-system etcd-tmp-server1 100m (2%) 0 (0%) 100Mi (1%) 0 (0%) 14m
kube-system kube-apiserver-tmp-server1 250m (6%) 0 (0%) 0 (0%) 0 (0%) 14m
kube-system kube-controller-manager-tmp-server1 200m (5%) 0 (0%) 0 (0%) 0 (0%) 14m
kube-system kube-proxy-znbnz 0 (0%) 0 (0%) 0 (0%) 0 (0%) 14m
kube-system kube-scheduler-tmp-server1 100m (2%) 0 (0%) 0 (0%) 0 (0%) 14m
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
Resource Requests Limits
-------- -------- ------
cpu 1100m (27%) 0 (0%)
memory 240Mi (3%) 340Mi (4%)
ephemeral-storage 100Mi (0%) 0 (0%)
hugepages-1Gi 0 (0%) 0 (0%)
hugepages-2Mi 0 (0%) 0 (0%)
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal NodeHasSufficientMemory 14m (x5 over 14m) kubelet Node tmp-server1 status is now: NodeHasSufficientMemory
Normal NodeHasNoDiskPressure 14m (x4 over 14m) kubelet Node tmp-server1 status is now: NodeHasNoDiskPressure
Normal NodeHasSufficientPID 14m (x5 over 14m) kubelet Node tmp-server1 status is now: NodeHasSufficientPID
Normal Starting 14m kubelet Starting kubelet.
Normal NodeHasSufficientMemory 14m kubelet Node tmp-server1 status is now: NodeHasSufficientMemory
Normal NodeHasNoDiskPressure 14m kubelet Node tmp-server1 status is now: NodeHasNoDiskPressure
Normal NodeHasSufficientPID 14m kubelet Node tmp-server1 status is now: NodeHasSufficientPID
Normal NodeAllocatableEnforced 14m kubelet Updated Node Allocatable limit across pods
Normal Starting 14m kube-proxy Starting kube-proxy.
Normal NodeReady 13m kubelet Node tmp-server1 status is now: NodeReady
修改Taints
# 污点策略后面要加一个“-”号表示去除它
kubectl taint nodes 污点策略-
例如：
kubectl taint nodes tmp-server1 node-role.kubernetes.io/master:NoSchedule-
如果当前就在master节点也可以
kubectl taint nodes `hostname` node-role.kubernetes.io/master:NoSchedule-
评论区