CODEWITHSUNDEEP
kuberneteskubernetes-ingressamazon-eks
user890234
user890234

Reputation: 995

AWS EKS kubernetes Deployments are not ready NodePort and LoadBalancer is not reachable

I am trying to deploy pods on the EKS cluster. Below are some screen shots which shows that AWS EKS cluster is created and is active, group nodes are also active, now when i try to deploy any pod like nginx, wordpress or something else, these are not in the ready state. I tried deploying kubernetes dashboard and its in ready state, but why others are not in ready state do not know and that's why their URLs are not reachable.

also, while checking logs it says as below: Error from server (NotFound): pods "deployment-2048-64549f6964-87d59" not found

EKS Cluster is running fine

Nodes are also ready

Deployments are not ready

LoadBalancer is created Command Line screenshot kubectl get ingress

Upvotes: 0

Views: 2184

Answers (1)

Sahadat Hossain
Sahadat Hossain

Reputation: 4351

Pods are in pending state. If a Pod is stuck in Pending it means that it can not be scheduled onto a node. It can happen because there are insufficient resources of one type or another that prevent pods scheduling.

You can look at the output by kubectl describe <deployment/pod_name>. There will be messages from the scheduler about why it can not schedule your pod.

Upvotes: 1

Related Questions