👀 Views: 184 💬 Answers: 1 📅 Created: 2025-06-14

aws eks ecr kubernetes YAML

I'm sure I'm missing something obvious here, but I've been working on this all day and I'm experiencing an scenario with my AWS EKS cluster where my pods are exploring in a `ImagePullBackOff` state. I have verified that the Docker image exists in the ECR repository and that the image URI in my deployment manifest is correct. Here's the snippet of my deployment file: ```yaml apiVersion: apps/v1 kind: Deployment metadata: name: my-app spec: replicas: 2 selector: matchLabels: app: my-app template: metadata: labels: app: my-app spec: containers: - name: my-container image: xxxxx.dkr.ecr.us-west-2.amazonaws.com/my-app:latest ports: - containerPort: 80 ``` I've attached the necessary IAM permissions to the EKS worker nodes for accessing the ECR repository. The IAM policy attached looks like this: ```json { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "ecr:GetAuthorizationToken", "ecr:BatchCheckLayerAvailability", "ecr:GetDownloadUrlForLayer", "ecr:BatchGetImage" ], "Resource": "*" } ] } ``` Despite this, when I describe the pod, I see the following behavior messages: ``` Failed to pull image "xxxxx.dkr.ecr.us-west-2.amazonaws.com/my-app:latest": rpc behavior: code = Unknown desc = behavior response from daemon: Head "https://xxxxx.dkr.ecr.us-west-2.amazonaws.com/v2/my-app/manifests/latest": no basic auth credentials ``` I have tried running `aws ecr get-login-password` and updating the kubeconfig, and the nodes have the necessary permissions. What could be causing this scenario? Are there any additional configurations I might be missing related to the EKS cluster or the worker nodes? Any help would be greatly appreciated! For reference, this is a production CLI tool. For context: I'm using Yaml on Linux. I'd really appreciate any guidance on this.