bored-table-20691
06/09/2021, 8:04 PMpulumi up
, and it created resources on my new cluster just fine, but is failing to delete the old resources since that EKS cluster no longer exists.
1. Is this expected?
2. How should I get out of this situation? The old resources can’t really exist by definition anymore since the EKS cluster is gone. pulumi refresh
errors out in the same way.steep-toddler-94095
06/09/2021, 8:07 PMpulumi stack rm
and start freshbored-table-20691
06/09/2021, 8:11 PMsteep-toddler-94095
06/09/2021, 8:12 PMpulumi state delete
for every k8s resourcebored-table-20691
06/09/2021, 8:15 PMsteep-toddler-94095
06/09/2021, 8:17 PMpulumi stack --show-urns
will give you all the URNs in your stack so you can just grep/filter for kubernetes resourcesbored-table-20691
06/09/2021, 8:19 PM$ pulumi state delete "urn:pulumi:tenant-itay8::okera-trial-tenants::kubernetes:apps/v1:Deployment::presto_coordinatorDeployment"
warning: This command will edit your stack's state directly. Confirm? Yes
Multiple resources with the given URN exist, please select the one to edit: [Use arrows to move, enter to select, type to filter]
> "itay8/presto-coordinator"
"itay8/presto-coordinator" (Pending Deletion)
Good to know multiple things with an URN can exist 🙂billowy-army-68599
06/09/2021, 8:19 PMbored-table-20691
06/09/2021, 8:20 PMbillowy-army-68599
06/09/2021, 8:22 PMpulumi stack export > stack.json
update the json to remove the resources
pulumi stack import --file stack.json
bored-table-20691
06/09/2021, 8:24 PM"delete": true
is set?