Open davisowb opened 1 month ago
Hi @davisowb,
I was able to reproduce this issue. It looks like this is how Terraform behaves when plan is available and the update operation fails with whatever reason. Please allow me to have a discussion with my team and I will come back to you with more details if I have any.
Thanks!
Terraform, Provider, Kubernetes and Helm Versions
Affected Resource(s)
Terraform Configuration Files
Steps to Reproduce
terraform plan -out=terraform.tfplan
terraform apply --auto-approve terraform.tfplan
)Error: Kubernetes cluster unreachable: the server has asked for the client to provide credentials
terraform plan -out=terraform.tfplan
Expected Behavior
The second plan should show same parameter changes to the
helm_release
resource as it did the first time around.Actual Behavior
First plan fails with:
Checking the cluster the planned changes are not applied (as expected due to auth failure)
2nd plan shows no changes, its like the changes got applied to state even though they were not actually implemented.
Community Note