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 figuring out the required configuration change was simple.

$ kubectl get nodes
NAME      STATUS   ROLES    AGE   VERSION
homelab   Ready    master   23h   v1.17.0$ kubectl describe node homelab
Name:               homelab
Roles:              master
Labels:             beta.kubernetes.io/arch=amd64beta.kubernetes.io/os=linuxkubernetes.io/arch=amd64kubernetes.io/hostname=homelabkubernetes.io/os=linuxnode-role.kubernetes.io/master=
Annotations:        kubeadm.alpha.kubernetes.io/cri-socket: /var/run/dockershim.sock                                             node.alpha.kubernetes.io/ttl: 0volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Sat, 28 Dec 2019 13:28:27 -0800
Taints:             node-role.kubernetes.io/master:NoSchedule
Unschedulable:      false

官方描述

And there it is – by default, kubeadm init configured this node as a Kubernetes master, which would normally take care for managing other Kubernetes "worker" (or "non-master") nodes. The Kubernetes Concepts documentation describes the distinction between the Kubernetes master and non-master nodes as follows:

The Kubernetes Master is a collection of three processes that run on a single node in your cluster, which is designated as the master node. Those processes are: kube-apiserver, kube-controller-manager and kube-scheduler.Each individual non-master node in your cluster runs two processes:kubelet, which communicates with the Kubernetes Master.kube-proxy, a network proxy which reflects Kubernetes networking services on each node.

So anyway, as soon as I saw node-role.kubernetes.io/master:NoSchedule I began nodding my head, realizing what the issue was. One Google search returned me straight back to the very installation guide I followed I had skimmed over, and the instruction I had skipped:

Control plane node isolation
By default, your cluster will not schedule pods on the control-plane node for security reasons. If you want to be able to schedule pods on the control-plane node, e.g. for a single-machine Kubernetes cluster for development, run:

kubectl taint nodes --all node-role.kubernetes.io/master-

With output looking something like:

node "test-01" untainted taint "node-role.kubernetes.io/master:" not found taint "node-role.kubernetes.io/master:" not found

This will remove the node-role.kubernetes.io/master taint from any nodes that have it, including the control-plane node, meaning that the scheduler will then be able to schedule pods everywhere.

So... one quick kubectl taint nodes --all node-role.kubernetes.io/master- command later, and my single-node K8s cluster was now actually useful for running pods!

NOTE: there's a LOT more output from kubectl describe node <node> that this; I'm just trimming the rest for brevity; all we needed was this clue about the configured Taints.

nodes are available: 1 node(s) had taints that the pod didn‘t tolerate相关推荐

『已解决』0/1 nodes are available: 1 node(s) had taints that the pod didn‘t tolerate.
k8s报错1 node(s) had taints that the pod didn‘t tolerate
这是由于我们在自己pod的yaml中没有添加容忍,加入容忍就可以了,可以看我之前的博客这里再补充一下当不清楚集群中node的污点时,可以用以下命令查看和删除污点 kubectl describe ...
Kubernetes default-scheduler 0/2 nodes are available: 2 node(s
K8S pod 调度失败问题解决问题问题这个问题其实很简单,因为deployment(或其他控制器)或Pod的yaml文件中使用了nodeSelector,例如:下面的这个yaml文件: ...
缩放节点池 0/1 nodes are available: 1 node(s) didn‘t match Pod‘s node affinity.
今天程序出问题了,某个namespace下的所有的Pods, 全部出于pending状态, 0/1 nodes are available: 1 node(s) didn't match Pod's ...
如何调整 k8s Node节点的最大可运行Pod数量
环境介绍: Ubuntu 20.04.3 LTS kubeadm安装的k8s集群1.21.8 Kubernetes Node节点默认允许最多创建110个Pod,如何调整Node节点的最大可运行Pod数 ...
default-scheduler 0/1 nodes are available: 1 node(s) had taint {node.kubernetes.io/disk-pressure: }
基于污点的驱逐 FEATURE STATE: Kubernetes v1.18 [stable] 前文提到过污点的 effect 值 NoExecute会影响已经在节点上运行的 Pod 如果 Pod ...
kubectl查看node状态_K8S故障排除方法 - 笃行之 - 博客园
1.查看pods哪些是有问题的,Runningg正常,其他异常: /opt/kubernetes/bin/kubectl get pods --all-namespaces -owide NAMESP ...
使用kubeadm 安装 kuberntes 1.13.3
# kubeadm安装kubernetes步骤说明: ## 第一步 ### 准备系统环境 - Repo仓库准备 1. docker-ce.repo 2. kubernetes.repo - 停用服务 ...
CentOS7系统上Kubernetes集群搭建
虚拟机创建在自己的Mac系统里面利用Parallels Desktop创建3台虚拟机,具体信息如下: CentOS7-Node1: 10.211.55.7 parallels/centos-test ...

nodes are available: 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相关推荐

最新文章

热门文章