Kubectl describe pod = 0/4 nodes are available 1 node(s) had taint {node.kubernetes.io/disk-pressure: }, that the pod didn’t tolerate, 3 node(s) didn’t match node selector.

This is because the node is tainted (pod’s YAML file is configured with node selector and bound to node label).

Linux:~ # kubectl get nodes -o json | jq '.items[].spec'
{
 "taints": [{"effect": "NoSchedule"."key": "node.kubernetes.io/disk-pressure"."timeAdded": "2021-03-06T14:15:27Z"}}]Copy the code

As you can see, the node is tainted with NoSchedule and cannot be scheduled to perform the following operations to unstain the name node.kubernetes. IO /disk-pressure on all nodes

Linux:~ # kubectl taint nodes --all node.kubernetes.io/disk-pressure-
node/k8s-w1 untainted
taint "node.kubernetes.io/disk-pressure" not found
taint "node.kubernetes.io/disk-pressure" not found
taint "node.kubernetes.io/disk-pressure" not found
Copy the code

Kubectl apply -f XXX. Yaml kubectl apply -f XXX. Yaml kubectl apply -f XXX. If it is still Pending, execute kubectl Describe Pod again to see the cause of the error