k8s master不可以被調度,修改deploy配置讓這個可以單獨調度上去

給兩個節點添加標籤,讓pod調度上去,但是kubectl describe pod  發現報錯了,因爲master不可以被調度,kube002也是設置了污點禁止被調度了

  Warning  FailedScheduling  4m33s (x2 over 9m34s)  default-scheduler  0/4 nodes are available:

1 node(s) had untolerated taint {key: kube002}, 1 node(s) had untolerated taint {node-role.kubernetes.io/master: },
2 node(s) didn't match Pod's node affinity/selector. preemption: 0/4 nodes are available: 4 Preemption is not helpful for scheduling..

查看不可以被調度,master節點

# kubectl describe node vm-qa-kubemaster001.xxm |grep -i schedulable
Unschedulable:      false

查看污點鍵值對

#kubectl describe node vm-qa-kubemaster001.zz.apus.com
Taints:             node-role.kubernetes.io/master:NoSchedule

這表示該節點有一個污點,鍵爲node-role.kubernetes.io/master,值爲空,效果爲NoSchedule

 

添加污點容忍度,指定調度節點

apiVersion: v1  
kind: Pod  
metadata:  
  name: my-pod  
spec:  
  containers:  
    - name: my-container  
      image: my-image  
  tolerations:  
    - key: "node-role.kubernetes.io/master"  
      operator: "Equal"  
      value: ""  
      effect: "NoSchedule"  
  nodeName: "vm-qa-kubemaster001.xxxm"

 新增如下:

  tolerations:  
    - key: "node-role.kubernetes.io/master"  
      operator: "Equal"  
      value: ""  
      effect: "NoSchedule"  
  nodeName: "vm-qa-kubemaster001.xxxm"

 

發表評論
所有評論
還沒有人評論,想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
相關文章