terraform
complains that the tags should not be the same as cluster tags.NOTE: Even when you modify the terraform state file to remove the tags, when you run a terraform plan
, it will detect the tags as new tags "to change".
However, terraform will still report the same error as below:
Error: Nodepool tags should not be same as cluster tags: key:tag_name, val:tag_value
│
│ with module.k8s-clusters.tanzu-mission-control_ekscluster.your-cluster-name[0],
│ on modules/clusters/your-cluster-nae.tf line 2, in resource "tanzu-mission-control_ekscluster" "your-cluster-name":
│ 2: resource "tanzu-mission-control_ekscluster" "your-cluster-name" {
terraform
file and run a terraform plan
, it will show no changes. terraform apply
errors out the same error as above, even though cluster tags are not being defined.TMC SaaS version
Kubernetes cluster running in EKS.
EKS cluster attached to TMC SaaS
The workaround for this is:
tags = { }
~ tags = {
+ "Application" = "Tanzu Kubernetes"
+ "Name" = "my-app-name"
+ "b_costcenter" = "some-id"
+ "b_env" = "env-name"
+ "b_module" = "some-module-name"
+ "b_program" = "my-program-name"
+ "b_role" = "some-role-name"
+ "b_service" = "some-svc-name"
}
~ tags = { }
terraform apply
terraform apply
.This bug is expected to be resolved in December of 2024.