https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
w
So - having to replace the cluster if you make significant network topology changes is expected.
gets stuck since it cant delete the resources for the now deleted cluster
This on the other hand isnt.
Deleting everything now fails with 
dial tcp: lookup <http://xxx.gr7.us-east-1.eks.amazonaws.com|xxx.gr7.us-east-1.eks.amazonaws.com>: no such host
Nor is this.
Can you recall the exact set of steps you took and at which steps you saw failures? I am wondering if this is a symptom of https://github.com/pulumi/pulumi/issues/2948.
f
Ah yes, that looks like a likely root cause
w
For this in particuar:
Deleting everything now fails with 
dial tcp: lookup <http://xxx.gr7.us-east-1.eks.amazonaws.com|xxx.gr7.us-east-1.eks.amazonaws.com>: no such host
It 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.
f
That sounds about right
w
In this case - the easiest remedy for now is to 
pulumi stack export > stack.json
and then remove all of the Kubernetes resources that no longer really exist, then 
pulumi stack import < stack.json
.
Alternativey - use 
pulumi state delete "<resource URN>"
on each Kubernetes resource URN to avoid having to manually edit the state file.
f
Ah, the second one sounds a bit nicer
Okay, thanks
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by