k8s报错1 node(s) had taints that the pod didn‘t tolerate

这是由于我们在自己pod的yaml中没有添加容忍，加入容忍就可以了，可以看我之前的博客

这里再补充一下

当不清楚集群中node的污点时，可以用以下命令查看和删除污点

kubectl describe nodes k8s-master |grep Taints
Taints:             gameble=true:NoSchedule[root@k8s-master ~]# kubectl describe nodes k8s-slave1 | grep Taints
Taints:             drunk=true:NoSchedule[root@k8s-master ~]# kubectl describe nodes k8s-slave2 | grep Taints
Taints:             smke=true:NoSchedule

根据上边命令查出来的污点名来删除污点。

gameble-

gameble就是污点名，后加减号就删掉了

[root@k8s-master ~]# kubectl taint node k8s-master gameble-
node/k8s-master untainted[root@k8s-master ~]# kubectl taint node k8s-slave1 drunk-
node/k8s-slave1 untainted[root@k8s-master ~]# kubectl taint node k8s-slave2 smke-
node/k8s-slave2 untainted

k8s报错1 node(s) had taints that the pod didn‘t tolerate相关推荐

nodes are available: 1 node(s) had taints that the pod didn‘t tolerate
首先.异常的发现 Troubleshooting was easy... kubectl describe node <node> revealed the taint, and figu ...
『已解决』0/1 nodes are available: 1 node(s) had taints that the pod didn‘t tolerate.
HBuilderX 安装 scss/sass编译插件报错 binding.node 解决方案windows版
HBuilderX 安装 scss/sass编译插件报错 binding.node 解决方案windows版官方给出的解决方案让我们在命令行执行下面三行代码 [0;31m--> LibSa ...
Calico 报错 calico/node is not ready: BIRD is not ready: BGP not established with（导致 K8S 集群网络无法使用）
错误今天不知道怎么回事,一台机器的calico-node报错,也就是无法初始化正常 Events:Type Reason Age From Message---- ------ ---- ---- ...
K8S 报错笔记--持续更新
一.ContainerCreating 这种报错其实不算报错,容器正在创建中,通常是我们配置问题导致的, 1.docker服务问题有一天起来有个应用说容器创建不出来,卡在ContainerCreat ...
spark on k8s报错：pods “spark-pi-4f2cd9772397764d-driver“ is forbidden: User “system:anonymous“
解决办法: #'指定集群中的匿名用户有管理员权限' [root@master ~]# kubectl create clusterrolebinding cluster-system-anonymou ...
K8s报错#!/bin/bash yum install -y yum-utils device-mapper-persistent-data lvm2 if [ $? = 0 ]；then echo
k8s在部署etcd单节点报错 failed to dial fab7ddbd0aa3e803 on stream Message (dial t-out) 这里需要安装docker环境,下面是doc ...
K8S报错network is not ready: container runtime network not ready
最近部署K8S真是踩坑很多,尤其是安装很完美,各种报错,最严重的就是查看pod节点发现 coredns名字开头的两个pod是启动不了,如图. 这问题是缺少配置文件创建配置文件 mkdir -p /e ...
K8s ❉ 报错 cannot be handled as a**
报错 [root@master ~]# kubectl create -f pod-nginx.yaml namespace/dev created Error from server (BadRe ...

k8s报错1 node(s) had taints that the pod didn‘t tolerate

k8s报错1 node(s) had taints that the pod didn‘t tolerate相关推荐

最新文章

热门文章