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
fix(eks-cluster-example): Add eks_worker_ami_name_filter variable to the example #32
Conversation
Unfortunately, most_recent (https://github.com/cloudposse/terraform-aws-eks-workers/blob/34a43c25624a6efb3ba5d2770a601d7cb3c0d391/main.tf#L141) variable does not work as expected, if you are not going to use custom ami you should enforce usage of eks_worker_ami_name_filter variable to set the right kubernetes version for EKS workers, otherwise will be used the first version of Kubernetes supported by AWS (v1.11) for EKS workers but EKS control plane will use the version specified by kubernetes_version variable.
Also I've updated readme with copy-paste to avoid the differences with an example 😄 |
/codefresh run test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @vymarkov , looks good
Please run terraform fmt
on all files including the examples.
And please rebuild README:
make init
make readme/deps
make readme
/codefresh run test |
@aknysh done |
/codefresh run test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @vymarkov
Unfortunately, most_recent variable does not work as expected.
Enforce usage of eks_worker_ami_name_filter variable to set the right kubernetes version for EKS workers,
otherwise will be used the first version of Kubernetes supported by AWS (v1.11) for EKS workers but
EKS control plane will use the version specified by kubernetes_version variable.