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.mcw.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"

 

案例如下：

apiVersion: v1  
kind: Pod  
metadata:  
  name: mcwtestcentos2-pod  
spec:  
  containers:  
    - name: mcwtestcentos2
      image: centos
      args:
      - /bin/sh
      - -c
      - sleep 60000000000000 
  restartPolicy: Always
  tolerations:  
    - key: "node-role.kubernetes.io/master"  
      operator: "Equal"  
      value: ""  
      effect: "NoSchedule"  
  nodeName: "kube001.x-sg-2.xx.com"



#  kubectl get pod --all-namespaces -o wide|grep kube001 |grep mcwtestcentos2
default         mcwtestcentos2-pod                                            1/1     Running            0          11h      10.x.1.75    kube001.xx-sg-2.xx.com         <none>           <none>