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

Upgrade cluster version is not supported #1246

Closed
1 of 4 tasks
mkamel93 opened this issue Feb 17, 2021 · 5 comments · Fixed by #1371
Closed
1 of 4 tasks

Upgrade cluster version is not supported #1246

mkamel93 opened this issue Feb 17, 2021 · 5 comments · Fixed by #1371

Comments

@mkamel93
Copy link

mkamel93 commented Feb 17, 2021

I have issues

I'm submitting a...

  • bug report
  • feature request
  • support request - read the FAQ first!
  • kudos, thank you, warm fuzzy

What is the current behavior?

I have provisioned an EKS cluster with Kubernetes version 1.18 successfully then I tried to update the Kubernetes version to 1.19 but when I am trying to run
terraform plan
I got the following error: Error: Your query returned no results. Please change your search criteria and try again.

If this is a bug, how to reproduce? Please include a code sample if relevant.

What's the expected behavior?

It should update the cluster kubernetes version same as updating it from the GUI

Are you able to fix this problem and submit a PR? Link here if you have already.

Environment details

  • Affected module version: v14.0.0
  • OS: Linux, Mac
  • Terraform version: v0.14.3

Any other relevant info

@jochen-st
Copy link

same with

Terraform v0.14.6

  • provider registry.terraform.io/hashicorp/aws v3.27.0
  • provider registry.terraform.io/hashicorp/helm v1.3.2
  • provider registry.terraform.io/hashicorp/kubernetes v2.0.2
  • provider registry.terraform.io/hashicorp/local v2.0.0
  • provider registry.terraform.io/hashicorp/null v3.0.0
  • provider registry.terraform.io/hashicorp/random v3.0.1
  • provider registry.terraform.io/hashicorp/template v2.2.0

@italolelis
Copy link

This is related to #1141. As proposed by @dbirks, a workaround would be to set

worker_ami_name_filter_windows = "Windows_Server-2019-English-Core-EKS_Optimized-1.18-*"

even if you don't have any windows servers, at least until AWS releases the windows version to 1.19.

It worked fine for me. Thanks to @dbirks.

@stale
Copy link

stale bot commented May 19, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@barryib
Copy link
Member

barryib commented May 19, 2021

I just opened #1371 to address this. Will you please review it and test it ?

@stale stale bot removed the stale label May 19, 2021
@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants