Open BBBmau opened 1 year ago
Same response as in https://github.com/hashicorp/terraform-provider-kubernetes/issues/1791#issuecomment-2015652590, this was fixed with PR #1831.
The workaround is to set the field_manager
for both kubernetes_node_taint and kubernetes_labels with 2 different values.
Terraform Version, Provider Version and Kubernetes Version
Affected Resource(s)
kubernetes_labels
kubernetes_node_taints
Terraform Configuration Files
Steps to Reproduce
terraform apply
terraform apply
Expected Behavior
What should have happened?
Should apply resource successfully after first apply and not attempt to apply on the second apply
Actual Behavior
What actually happened?
on second apply it will apply the node taints despite already creating it in the first apply.
The third apply will result in the labels from
kubernetes_labels
to be missing leading it needing to be created once moreImportant Factoids
References
Community Note