Open rhart opened 3 years ago
I'm not great at reading Go, but I think it's due to trying to run eksctl utils write-kubeconfig --cluster=<name>
and the cluster does not exist. Is it possible in that case to mark the resource as needs creating again?
I faced exactly the same issue, in my case i was assigning kubeconfig_path
in resource "eksctl_cluster"
to predefined path, as it was creating new path every time if i run terraform plan
.
It has broken my terraform state, but I restored it from old version of terraform state.
At last I have given up the idea to set kubeconfig_path
to restore back to original position.
I'm having exact same issue, any resolution @rhart ?
After successfully creating a cluster, then deleting the cluster outside of Terraform, and then running a
terraform plan
, I get the following error:I was expecting that the provider would detect the cluster was deleted and then recreate it. Do I have the wrong expectations?