0/4 nodes are available: 4 Preemption is not helpful for scheduling.
Quote from moshe on 30/08/2022, 12:45 pmProblem
User gets the following error when running the command
kubectl get pods
pod/minio-5f6cdb6b7d-dcgd5 0/1 Pending 0 24s
kubectl describe pod/minio-5f6cdb6b7d-dcgd5
Warning FailedScheduling 41s default-scheduler 0/4 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/master: }, 4 node(s) didn’t match Pod’s node affinity/selector. preemption: 0/4 nodes are available: 4 Preemption is not helpful for scheduling.
Solution
The node selector you specified is incorrect
helm install minio –set auth.existingSecret=bitnami-minio-credentials –set resources.requests.memory=2048Mi –set persistence.size=1000Gi –set nodeSelector.service=MYNODE –version 9.3.0 bitnami/minio
Name MYNODE specified is not the right name of the node change it accordingly
you can find your node names
kubectl get nodes -o wide
Problem
User gets the following error when running the command
kubectl get pods
pod/minio-5f6cdb6b7d-dcgd5 0/1 Pending 0 24s
kubectl describe pod/minio-5f6cdb6b7d-dcgd5
Warning FailedScheduling 41s default-scheduler 0/4 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/master: }, 4 node(s) didn’t match Pod’s node affinity/selector. preemption: 0/4 nodes are available: 4 Preemption is not helpful for scheduling.
Solution
The node selector you specified is incorrect
helm install minio –set auth.existingSecret=bitnami-minio-credentials –set resources.requests.memory=2048Mi –set persistence.size=1000Gi –set nodeSelector.service=MYNODE –version 9.3.0 bitnami/minio
Name MYNODE specified is not the right name of the node change it accordingly
you can find your node names
kubectl get nodes -o wide