Closed as not planned
Description
What Happened?
I'm using Minikube on an AWS EC2 instance (amazonlinux2023) running Kubernetes v1.29.1 with 'Containerd' as the container runtime.
The goal is to pull images from a private Amazon ECR repository using the EC2 IAM instance role permissions, without storing explicit credentials.
Everything was working fine with just the IAM instance role until I've decided to upgrade the k8s version from v1.26.1.
However, when Minikube attempts to pull these images in pods, it fails with an authentication error (e.g., "no basic auth credentials").
How can I configure Minikube to use the EC2 IAM instance role for pulling images access, just as it worked before?
How to reproduce:
- Create a minikube cluster with k8s v1.26.1
- Run a pod with an image from private ECR repository
kubectl run <pod_name> --image '<account_id>.dkr.ecr.<region>.amazonaws.com/nginx:latest'
- Observe a running pod - successful image pull
- Delete minikube cluster
- Create a new minikube cluster with k8s version >v1.26.1
- Run a pod with an image from private ECR repository
kubectl run <pod_name> --image '<account_id>.dkr.ecr.<region>.amazonaws.com/nginx:latest'
- Observe a failed pod - image pull failure
Failed to pull image "<account_id>.dkr.ecr.<region>.amazonaws.com/nginx:latest": failed to pull and unpack image "<account_id>.dkr.ecr.<region>.amazonaws.com/nginx:latest": failed to resolve reference "<account_id>.dkr.ecr.<region>.amazonaws.com/nginx:latest": pull access denied, repository does not exist or may require authorization: authorization failed: no basic auth credentials
Operating System
Other
Driver
None (Baremetal)