CoreDNS Pod ErrImagePull issue

0

I have created one fargate profile for EKS cluster, after that the coreDNS pods were in pending state so i restarted the CoreDNS Deployment after this one Pod was running and 2nd pod is having image pull issue, i tried deleting the pods and recreating it but same issue.

Note - Ec2 compute annotation is not there in coreDNS deployment

asked 2 months ago190 views
4 Answers
0

One Pod is running when restarting the deployment. For the 2nd Pod if we delete it 2-3 time then it is also running

answered 2 months ago
  • It depends on which subnet is assigned. If fargate is configured to launch in public and private subnets, any of the subnet might be assigned. Assuming private subnet does not have a route via NAT, and the pod is configured in one of the private subnets, the pod might be pending. (Just elaborating on the possible cause I mentioned). Image is not a problem. You mentioned that if you delete 2 or 3 times then it run. Check which subnets it's assigned to when in pending state (assuming AWS console shows that ) and compare with pod 1.

0

Hi,

How is the VPC configured? Does it have Public and private subnets? Which subnets are assigned to the fargate profile. Do the private subnets have default routes assigned via NAT gateway / NAT instance?

With limited info available, one possible reason I can think of is that the non running pod is scheduled in the private subnet with no internet access and hence is pending. You might want to rule this out.

--Syd

profile picture
Syd
answered 2 months ago
0

For one pod it is able to pull the image and for another pod it is giving error. The image URL is same for both. Sometimes both are not running after restarting multiple times they are running

answered 2 months ago
0

Troubleshooting CoreDNS Pending State, as per: https://repost.aws/knowledge-center/eks-resolve-pending-fargate-pods

  1. Confirm no default annotation for EC2 compute type in CoreDNS deployment.
  2. Ensure CoreDNS pods selectors match a Fargate profile in the cluster.
  3. Check Fargate profile and pod specs for compatible VPC subnets and IAM roles.
  4. Investigate pod events and describe pods for image pull failure clues.
  5. Delete one CoreDNS pod to isolate the issue.
  6. Deploy a simple pod with the same image for testing image pull success.
profile picture
EXPERT
answered 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions