fresh-flag-12765
07/19/2019, 5:23 PMdial tcp: lookup <http://xxx.gr7.us-east-1.eks.amazonaws.com|xxx.gr7.us-east-1.eks.amazonaws.com>: no such host
white-balloon-205
gets stuck since it cant delete the resources for the now deleted clusterThis on the other hand isnt.
Deleting everything now fails withNor is this.dial tcp: lookup <http://xxx.gr7.us-east-1.eks.amazonaws.com|xxx.gr7.us-east-1.eks.amazonaws.com>: no such host
fresh-flag-12765
07/19/2019, 5:25 PMwhite-balloon-205
Deleting everything now fails withIt sounds like you have managed to delete your cluster without deleting the Kubernetes resources installed in it. That should not be possible, but I believe due to 2948 above it could be if you had otehr failures previously.dial tcp: lookup <http://xxx.gr7.us-east-1.eks.amazonaws.com|xxx.gr7.us-east-1.eks.amazonaws.com>: no such host
fresh-flag-12765
07/19/2019, 5:26 PMwhite-balloon-205
pulumi stack export > stack.json
and then remove all of the Kubernetes resources that no longer really exist, then pulumi stack import < stack.json
.pulumi state delete "<resource URN>"
on each Kubernetes resource URN to avoid having to manually edit the state file.fresh-flag-12765
07/19/2019, 5:28 PM