aws / aws/eks-anywhere

Unable to install eks anywhere with kindnetd cni due to image tags in public.ecr.aws have been changed.

Open
#7,264 12 comments 0 reactions 0 assignees View on GitHub
external
Dominant language
Go
Stars
2.1k
Forks
328
Avg merge
1d 4h
Merged PRs (30d)
9

Description

**What happened**:
kindnetd image tag has been changed on public.ecr.aws from v0.18.0 to v0.18.0-eks-a-45

**What you expected to happen**:
This cause issue to install eks anywhere on docker when cillium cni has issue to start.

**How to reproduce it (as minimally and precisely as possible)**:
on clean docker factory setting.
run

`CLUSTER_NAME=mgmt
eksctl anywhere generate clusterconfig $CLUSTER_NAME \
--provider docker > $CLUSTER_NAME.yaml`

Then update mgmt.yaml from cilium to kindnetd
Then run
`eksctl anywhere create cluster -f $CLUSTER_NAME.yaml`

then use docker ps to inspect hang installation and you will see the image was unable to be pulled down for cni.

**Anything else we need to know?**:

**Environment**:
- EKS Anywhere Release: 0.18.3
- EKS Distro Release: 1.28

Contributor guide

Open the contributing guide

Research direction

Reproduce the failure with the provided eksctl anywhere generate clusterconfig and create cluster commands, then inspect mgmt.yaml and the Docker containers with docker ps. Trace the kindnetd image reference used for the Docker provider and update it to the available public.ecr.aws tag. Done means a clean Docker installation can pull the kindnetd image and complete cluster creation.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
infrastructure
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.