eksctl-io / eksctl

The official CLI for Amazon EKS
https://eksctl.io
Other
4.92k stars 1.41k forks source link

[Bug] eksctl update-aws-node updated aws-eks-nodeagent to an invalid image in AWS GovCloud #7999

Open 1riggs opened 6 days ago

1riggs commented 6 days ago

What were you trying to accomplish?

As part of administering an EKS Cluster in AWS GovCloud, us-gov-west-1, I upgraded the cluster version (from v1.26 -> v1.27). As per the documentation I was updating the addons, including aws-node. To that end, I ran eksctl utils update-aws-node --cluster my-cluster.

I expected the aws-node DaemonSet to update with the appropriate container versions, as documented in the eksctl documentation.

What happened?

Updated configuration included 602401143452.dkr.ecr.us-west-2.amazonaws.com/amazon/aws-network-policy-agent:v1.1.1. This results in errors when pulling that image for the aws-eks-nodeagent:

ImagePullBackOff (Back-off pulling image "602401143452.dkr.ecr.us-west-2.amazonaws.com/amazon/aws-network-policy-agent:v1.1.1")

How to reproduce it?

Run the aforementioned command after a cluster version update in the AWS GovCloud region, us-gov-west-1.

Logs

N/A

Anything else we need to know?

Suspect the registry/region for the aws-eks-nodeagent is incorrect. The other apps in that DaemonSet (aws-node & aws-vpc-cni-init) use 013241004608.dkr.ecr.us-gov-west-1.amazonaws.com.

Versions

$ eksctl info
eksctl version: 0.192.0
kubectl version: v1.25.16
OS: linux
github-actions[bot] commented 6 days ago

Hello 1riggs :wave: Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website

1riggs commented 6 days ago

Manually modifying the DeamonSet to use 013241004608.dkr.ecr.us-gov-west-1.amazonaws.com/amazon/aws-network-policy-agent:v1.1.1 does work.