Kubernetes: EKS – Warning FailedScheduling – default-scheduler no nodes available to schedule pods

I spun up an EKS cluster and, when I ran:

kubectl get pods -n kube-system

got

 

More detail needed:

kubectl describe pods -n kube-system

Warning FailedScheduling 2m13s (x345 over 102m) default-scheduler no nodes available to schedule pods

 

Looking in EC2 Instances, I could see 2 EKS nodes running with the correct AMI IDs.

But Kubernetes can’t see these nodes. E.g.

kubectl get nodes

No resources found.

Note: low level objects like nodes aren’t namespaced –¬†https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/#not-all-objects-are-in-a-namespace

 

 

 

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *