-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] eksctl update-aws-node updated aws-eks-nodeagent to an invalid image in AWS GovCloud #7999
Comments
Manually modifying the DeamonSet to use |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
I ran into this same issue running:
The image gets updated to image: 602401143452.dkr.ecr.us-west-2.amazonaws.com/amazon/aws-network-policy-agent:v1.1.1
|
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 raneksctl 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: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
The text was updated successfully, but these errors were encountered: