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 Cluster Tag conflict with Nodepool Tags #417

Closed
JuanFCabrera opened this issue Oct 2, 2024 · 2 comments · Fixed by #463
Closed

EKS Cluster Tag conflict with Nodepool Tags #417

JuanFCabrera opened this issue Oct 2, 2024 · 2 comments · Fixed by #463
Labels
bug Bug stale Stale

Comments

@JuanFCabrera
Copy link

Describe the bug

removed cluster tags are still reported and preventing nodepool tags from being created, TMC, AWS and TF Statefile do not show any cluster level tags.

Error: Nodepool tags should not be same as cluster tags: key:b_program, val:connected_fleet

with module.k8s-clusters.tanzu-mission-control_ekscluster.acceptance-run-streams[0],
on modules/clusters/acceptance-run-streams.tf line 2, in resource "tanzu-mission-control_ekscluster" "acceptance-run-streams":
2: resource "tanzu-mission-control_ekscluster" "acceptance-run-streams" {

Reproduction steps

  1. created cluster with tags at cluster level
    2.created nodepool tags and removed cluster tags
    3.tf apply fails due to cluster tags that do not exist
    ...

Expected behavior

nodepool tags should be created and cluster tags removed

Additional context

No response

@JuanFCabrera JuanFCabrera added the bug Bug label Oct 2, 2024
@JuanFCabrera
Copy link
Author

Providing additional context,

  1. looks like terraform is able to create tags only at a cluster level, terraform is able to create and update cluster tags
  2. terraform does not recognize removal of cluster level tags, running terraform plan returns no difference.
  3. nodepool tags cannot be the same as previously created cluster tags.

Copy link

'Marking this issue as stale due to inactivity. This helps us focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context.
Thank you!'

@github-actions github-actions bot added the stale Stale label Dec 14, 2024
@vivgoyal vivgoyal linked a pull request Dec 17, 2024 that will close this issue
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug stale Stale
Projects
None yet
1 participant