nodes had volume node affinity conflict

keywords

1 node(s) had taints that the pod didn't tolerate, 2 node(s) had volume node affinity conflict.

background

 
helm delete tidb-cluster --purge 

销毁tidb cluster 之后，再次部署tidbcluster后发现 tikv都是pending，describe发现如下

 Warning  FailedScheduling            tidb-scheduler  0/4 nodes are available: 1 node(s) had taints that the pod didn't tolerate, 2 node(s) had volume node affinity conflict.
 Warning  FailedScheduling            tidb-scheduler  0/4 nodes are available: 1 node(s) had taints that the pod didn't tolerate, 2 node(s) had volume node affinity conflict.

 Warning  HAScheduling      70s (x2 over 70s)  tidb-scheduler  pods "tidb-cluster-tikv-3" not found 

1个节点存在pod无法容忍的污染，2个节点存在卷节点亲和冲突

analyze

是之前数据卷中的数据没清理导致的

solve

删除之前的数据

 
kubectl get pv -l app.kubernetes.io/namespace=tidb -o name | xargs -I {} kubectl patch {} -p '{"spec":{"persistentVolumeReclaimPolicy":"Delete"}}' && \

kubectl delete pvc --namespace tidb --all 

删除之前的数据后 ，再重新 helm install tidb-cluster

SEURL:

1.范式

Relevance