Skip to content
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

Support for Amazon EKS 1.12 Clusters #679

Closed
christopherhein opened this issue Mar 28, 2019 · 3 comments · Fixed by #680
Closed

Support for Amazon EKS 1.12 Clusters #679

christopherhein opened this issue Mar 28, 2019 · 3 comments · Fixed by #680

Comments

@christopherhein
Copy link
Contributor

Before creating a feature request, please search existing feature requests to see if you find a similar one. If there is a similar feature request please up-vote it and/or add your comments to it instead

Why do you want this feature?
Everyone should be able to use the latest EKS version. :)

aws/containers-roadmap#24

What feature/behavior/change do you want?
Support for create'ing and update'ing existing clusters with Kubernetes 1.12.

Do not hesitate, when appropriate, to share the exact commands or API you would like, and/or to share a diagram (e.g.: asciiflow.com): "a picture is worth a thousand words".

@whereisaaron
Copy link

whereisaaron commented Mar 29, 2019

It looks like it is always the case we need to update eksctl and cut a new release before we can upgrade to a new k8s version. Is there sufficient AW API to enable discovering the available control plane version and matching AMI versions? Or it inevitably a manual task?

@tabern
Copy link

tabern commented Mar 29, 2019

@whereisaaron I think this will solve the problem you are describing aws/containers-roadmap#231

@whereisaaron
Copy link

That sounds great for the AMI versions @tabern. @errordeveloper also mentioned that there is also currently no way to know what control plane versions are available? (to CF)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants