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 Auto Mode - Failed to create when node_pools is not set, node_role_arn is set #3238

Closed
1 task done
erezzarum opened this issue Dec 11, 2024 · 2 comments · Fixed by #3239
Closed
1 task done

EKS Auto Mode - Failed to create when node_pools is not set, node_role_arn is set #3238

erezzarum opened this issue Dec 11, 2024 · 2 comments · Fixed by #3239

Comments

@erezzarum
Copy link

erezzarum commented Dec 11, 2024

Description

  • ✋ I have searched the open/closed issues and my issue is not listed.

Using EKS Auto Mode without providing nodepools fails.

⚠️ Note

Before you submit an issue, please perform the following first:

  1. Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
  2. Re-initialize the project root to pull down modules: terraform init
  3. Re-attempt your terraform plan or apply and check if the issue still persists

Versions

  • Module version [Required]: 20.31.1

  • Terraform version: 1.73

  • Provider version(s): 5.80.0

Reproduction Code [Required]

Steps to reproduce the behavior:

module "eks" {
...
...
  cluster_compute_config = {
    enabled = true
  }
...
...
}

Expected behavior

Enable EKS Auto Mode without any pre-defined nodepools but create the node role.

Actual behavior

Fail to create cluster, as nodepools can not be empty if node role is provided, which is provided by default regardless if nodepools is set or no.

Terminal Output Screenshot(s)

Error: creating EKS Cluster (cluster-demo): operation error EKS: CreateCluster, https response error StatusCode: 400, RequestID: 9055f212-bdb4-4157-b03f-ce3addb3532d, InvalidParameterException: When Compute Config nodeRoleArn is not null or empty, nodePool value(s) must be provided.

Additional context

@antonbabenko
Copy link
Member

This issue has been resolved in version 20.31.2 🎉

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 Jan 12, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants