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

AWS EKS Managed Node Group creates a new launch template version on every run if enable_monitoring = false #3299

Closed
1 task done
ib-ak opened this issue Feb 13, 2025 · 2 comments

Comments

@ib-ak
Copy link

ib-ak commented Feb 13, 2025

Description

AWS EKS Node Group creates a new launch template version every time if enable_monitoring = false

dynamic "monitoring" {
for_each = var.enable_monitoring ? [1] : []
content {
enabled = var.enable_monitoring
}
}

when enable_monitoring is false terraform will remove the enabled = false under monitoring

monitoring {
 - enabled = false -> null
 } 

If your request is for a new feature, please use the Feature request template.

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

⚠️ 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]: 19.21.0

  • Terraform version: 1.3

  • Provider version(s): 4.67

Reproduction Code [Required]

Run the example
https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/examples/eks-managed-node-group/eks-al2.tf

Steps to reproduce the behavior:

  1. deploy this https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/examples/eks-managed-node-group/eks-al2.tf
  2. redeploy it again without making any changes

Expected behavior

launch template should not change if there are no changes.

Actual behavior

a new version of launch template on every subsequent runs.

Copy link

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Mar 20, 2025
Copy link

This issue was automatically closed because of stale in 10 days

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants