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

eks_node_group does not select correct default release_version on version upgrade #907

Closed
1 of 4 tasks
Nuru opened this issue Jun 4, 2020 · 2 comments
Closed
1 of 4 tasks

Comments

@Nuru
Copy link

Nuru commented Jun 4, 2020

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?

When upgrading a node group from Kubernetes 1.15 to 1.16 and setting release_version = null, the upgrade fails because the selected Release Version is a 1.15 version, not a 1.16 version.

Error: error updating EKS Node Group (test-cluster:test-eks-us-east-2a-workers) version: InvalidParameterException: Requested Nodegroup release version 1.15.10-20200228 is invalid. Allowed release version is 1.16.8-20200531

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

  • Create an EKS cluster using resource "aws_eks_cluster" using version = "1.15"
  • Create a node group in that cluster using resource "aws_eks_node_group" with release_version = null and version = "1.15"
  • Upgrade the cluster by changing "aws_eks_cluster" to version = "1.16"
  • Upgrade the node group by changing "aws_eks_node_group" to version = "1.16"

What's the expected behavior?

Node group is upgraded to latest 1.16 release AMI

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

No

Environment details

  • Affected module version: AWS 2.64.0
  • OS: Alpine 3.11.6
  • Terraform version: 0.12.26

Any other relevant info

@Nuru
Copy link
Author

Nuru commented Jun 4, 2020

Sorry, this is an upstream issue hashicorp/terraform-provider-aws#12675

@Nuru Nuru closed this as completed Jun 4, 2020
@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 26, 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

No branches or pull requests

1 participant