Warning FailedScheduling 8s default-scheduler 0/3 nodes are available: 1 Insufficient memory

问题

ka get pod -o wide

ka describe pod oracle-265abd451-0

Pod无法调度

Warning FailedScheduling 8s default-scheduler 0/3 nodes are available: 1 Insufficient memory, 1 node(s) had taint {node.kubernetes.io/not-ready: }, that the pod didn’t tolerate, 1 node(s) had volume node affinity conflict.

默认调度程序0/3个节点可用:1个内存不足,1个节点具有pod无法容忍的污点{node.kubernetes.io/not-ready:},1个节点具有卷节点亲和力冲突。

排查思路

查看节点状态:发现有一个节点NotReady

k get node

查看标签

k get nodes --show-labels

查看污点

k get node -o yaml |grep taint -A 5
          f:taints: {}
      manager: kube-controller-manager
      operation: Update
      time: "2022-07-19T12:49:26Z"
    name: x-x-x-x
    resourceVersion: "233927"
--
    taints:
    - effect: NoSchedule
      key: node.kubernetes.io/not-ready
      timeAdded: "2022-07-19T12:49:26Z"
    - effect: NoExecute
      key: node.kubernetes.io/not-ready
--
          f:taints: {}
        f:status:
          f:conditions:
            k:{"type":"DiskPressure"}:
              f:lastTransitionTime: {}
              f:message: {}
--
    taints:
    - effect: NoSchedule
      key: node.kubernetes.io/unreachable
      timeAdded: "2022-07-19T12:45:33Z"
    - effect: NoExecute
      key: node.kubernetes.io/unreachable
kubectl taint nodes node{1,2,3} node-role.kubernetes.io/master:NoSchedule

清除污点

k taint nodes --all node-role.kubernetes.io/master-
taint "node-role.kubernetes.io/master" not found
taint "node-role.kubernetes.io/master" not found
taint "node-role.kubernetes.io/master" not found
k get node -o yaml |grep taint -A 5 

没了。。。

重启Pod后正常。。。

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值