-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
data aws_ami "eks_worker" is failing in ap-east-1 #480
Comments
Looks like it. Strange. |
Internally we've applied temp. workaround in ...
owners = ["602401143452", "800184023465"]
... but this is not the solution as 800184023465 does not contain images with relevant names :) |
I seem to be having the same issue in us-east-1. Here is what I am seeing?
A pick at the code shows this:
I did not add any additional filter. affected version: |
It turns out my cluster version was incorrect. Cluster version should not contain minor release, it should be for example 1.14. See this https://github.com/awslabs/amazon-eks-ami and this for https://docs.aws.amazon.com/eks/latest/userguide/eks-optimized-ami.html for details. |
@bsakweson I had the same issue today when I tried upgrading to 1.14.6. Maybe the docs/README could be updated to reflect that only the major version should be specified. |
@vranystepan - Does the @bsakweson's comment help you ? |
This should specified in the AWS EKS documentation. You must only provider major version for EKS cluster. AWS handle minor upgrades for you. You can send a PR for that https://github.com/awsdocs/amazon-eks-user-guide @vranystepan I'm closing this issue. Feel free to re-open it if the provided "solution" doesn't work for you. |
@barryib the issue is not related to EKS version. If you check @vranystepan's |
I have the same issue but it was about cluster_version variable which I have set it to 1.22 but it worked with 1.20 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
I have issues
We are not able to create EKS cluster in
ap-east-1
due to issues with AMI names.I'm submitting a...
What is the current behavior?
With any ami we are getting
We suppose that EKS module is always trying to find images (before
workers_group_defaults_defaults
is being merged withvar.workers_group_defaults
) with following pattern but apparently there are no such images in the HK region.I'm not able to receive any results even with CLI:
Environment details
Any other relevant info
Perhaps there is different owner in HK region? https://github.com/awslabs/amazon-eks-ami/pull/305/files/fd9cf4458dffa1e9c01a3a42fca1cc7690abc504
The text was updated successfully, but these errors were encountered: