# 0/1 nodes are available: 1 node(s) had untolerated taint

**URL:** <https://discuss.kubernetes.io/t/0-1-nodes-are-available-1-node-s-had-untolerated-taint/23248>\
**Category:** General Discussions\
**Created:** [February 28, 2023, 3:31pm UTC](https://discuss.kubernetes.io/t/0-1-nodes-are-available-1-node-s-had-untolerated-taint/23248 "2023-02-28T15:31:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![lreis09](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/lreis09/32/11929_2.png) [@lreis09](https://discuss.kubernetes.io/u/lreis09)\
**Post date:** [February 28, 2023, 3:31pm UTC](https://discuss.kubernetes.io/t/0-1-nodes-are-available-1-node-s-had-untolerated-taint/23248/1 "2023-02-28T15:31:08Z")

</div>

### What happened?

Hi, i have a problem when i launch a pod the state of the pod is pending.  
The command “kubectl describe pods apache-7f6fddb7df-q229r” and the output is " Warning FailedScheduling 61s (x2 over 6m23s) default-scheduler 0/1 nodes are available: 1 node(s) had untolerated taint {[node-role.kubernetes.io/control-plane:](http://node-role.kubernetes.io/control-plane:) }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.."  
Logs of the pod is none, the service kubelet, docker and containerd is running without any errors.  
Journalctl not giving me anything.  
My OS is Debian 11

### What did you expect to happen?

I expected the state pod is running.  
Please help me and thanks for the help.

### How can we reproduce it (as minimally and precisely as possible)?

Install docker and kubernettes by the documentations.

### Kubernetes version

Client Version: v1.26.1 Kustomize Version: v4.5.7 Server Version: v1.26.1

### OS version

# On Linux:

$ cat /etc/os-release  
PRETTY\_NAME=“Debian GNU/Linux 11 (bullseye)”  
NAME=“Debian GNU/Linux”  
VERSION\_ID=“11”  
VERSION=“11 (bullseye)”  
VERSION\_CODENAME=bullseye  
ID=debian  
HOME\_URL=“[https://www.debian.org/](https://www.debian.org/)”  
SUPPORT\_URL=“[https://www.debian.org/support](https://www.debian.org/support)”  
BUG\_REPORT\_URL=“[https://bugs.debian.org/](https://bugs.debian.org/)”

Linux docker 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86\_64 GNU/Linux

---

<div class="post-metadata">

**Author:** ![protosam](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/protosam/32/7732_2.png) [@protosam](https://discuss.kubernetes.io/u/protosam)\
**Post date:** [March 1, 2023, 7:42pm UTC](https://discuss.kubernetes.io/t/0-1-nodes-are-available-1-node-s-had-untolerated-taint/23248/2 "2023-03-01T19:42:33Z")

</div>

You missed a step.

> **[Creating a cluster with kubeadm](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#control-plane-node-isolation)**
>
> Using kubeadm, you can create a minimum viable Kubernetes cluster that conforms to best practices. In fact, you can use kubeadm to set up a cluster that will pass the Kubernetes Conformance tests. kubeadm also supports other cluster lifecycle...

---

<div class="post-metadata">

**Author:** ![ivanaevsky](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/ivanaevsky/32/12141_2.png) [@ivanaevsky](https://discuss.kubernetes.io/u/ivanaevsky)\
**Post date:** [March 29, 2023, 10:38am UTC](https://discuss.kubernetes.io/t/0-1-nodes-are-available-1-node-s-had-untolerated-taint/23248/3 "2023-03-29T10:38:55Z")

</div>

Thank you!

---

<div class="post-metadata">

**Author:** ![Minaxi\_Joshi](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/minaxi_joshi/32/14919_2.png) [@Minaxi\_Joshi](https://discuss.kubernetes.io/u/Minaxi_Joshi)\
**Post date:** [May 7, 2024, 7:22am UTC](https://discuss.kubernetes.io/t/0-1-nodes-are-available-1-node-s-had-untolerated-taint/23248/6 "2024-05-07T07:22:27Z")

</div>

Hi,

I am getting

Events:  
Type Reason Age From Message

* * *

Warning FailedScheduling 55s (x2 over 82s) default-scheduler 0/2 nodes are available: 1 Insufficient memory, 1 node(s) had untolerated taint {[node-role.kubernetes.io/control-plane:](http://node-role.kubernetes.io/control-plane:) }. preemption: 0/2 nodes are available: 1 No preemption victims found for incoming pod, 1 Preemption is not helpful for scheduling.

resource.yaml is:  
apiVersion: apps/v1  
kind: Deployment  
metadata:  
name: resource-pod  
labels:  
app: resource  
spec:  
replicas: 2  
selector:  
matchLabels:  
app: resource  
template:  
metadata:  
labels:  
app: resource  
spec:  
containers:  
- name: resource-demo  
image: polinux/stress  
command: [“stress”]  
args: [“–cpu”,“2”,“–vm”, “1”, “–vm-bytes”,“1G”, “–vm-hang”,“1”]  
resources:  
requests:  
memory: “2Gi”  
cpu: “1”  
limits:  
memory: “3Gi”  
cpu: “1”  
livenessProbe:  
exec:  
command:  
- echo “hello”  
failureThreshold: 2  
periodSeconds: 2

I understood the issue, as I have requested for 2Gi of memory to start a pod and requested for 2 pods (2\*2 = 4Gi) memory. but my node is having allocatable memory of 3849628Ki ie 3 Gi

kubectl describe node worker-node

Hostname: k8s-worker  
Capacity:  
cpu: 3  
ephemeral-storage: 47109660Ki  
hugepages-2Mi: 0  
memory: 3849628Ki  
pods: 110  
Allocatable:  
cpu: 3  
ephemeral-storage: 43416262585  
hugepages-2Mi: 0  
memory: 3747228Ki  
pods: 110