AWS EKS image hard-coded for us-west-2 region

Bug #1776498 reported by Robert C Jennings
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-images
Fix Released
Undecided
Robert C Jennings

Bug Description

In var/lib/cloud/scripts/per-instance/00-EKS-config.sh on the us-east-1 image at https://cloud-images.ubuntu.com/aws-eks/, if you look at how CLUSTER_NAME is set, the region is hardcoded to us-west-2. This prevents kubelet from ever starting.

Robert C Jennings (rcj)
tags: added: id-5b1fe428921dc37b0380b164
Robert C Jennings (rcj)
Changed in cloud-images:
status: New → In Progress
assignee: nobody → Robert C Jennings (rcj)
Revision history for this message
Robert C Jennings (rcj) wrote :

New images have been built and published that resolve this issue. They also bring in additional changes that require the latest nodegroup template.

See http://cloud-images.ubuntu.com/aws-eks/ for the latest AMI ID and Template download.

Revision history for this message
Robert C Jennings (rcj) wrote :
Changed in cloud-images:
status: In Progress → Fix Released
Revision history for this message
Jason Kriss (jasonkriss) wrote :

Confirmed this is working for me. Thanks a lot Robert!

Revision history for this message
Shiva (shivapk) wrote :

Today, I launched an EKS cluster with Ubuntu AMI (ami-6d622015) and noticed that there is no response for 'kubectl get nodes --watch' command. Also tried to deploy the Guest Book application mentioned in EKS getting started guide but no success.

Revision history for this message
Dan Watkins (oddbloke) wrote :

Hi Shiva,

That sounds like a separate issue; could you file a new bug (if you are still seeing the problem), please?

Thanks!

Dan

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.