This message was deleted.
# generals
sparse-intern-71089
07/08/2022, 1:42 AMThis message was deleted.
b
billowy-army-68599
07/08/2022, 1:44 AM
is your cluster unreachable?
m
magnificent-helicopter-3467
07/08/2022, 1:44 AMYes, it’s deleted
b
billowy-army-68599
07/08/2022, 1:45 AM
set the environment variables
PULUMI_K8S_DELETE_UNREACHABLEpulumi refresh✅ 1
billowy-army-68599
07/08/2022, 1:46 AM
PULUMI_K8S_DELETE_UNREACHABLE=truem
magnificent-helicopter-3467
07/08/2022, 1:48 AMGet the same error
magnificent-helicopter-3467
07/08/2022, 1:55 AMI believe the state is very out of sync now. It doesn’t include resources that are there, and it includes resources that have been deleted/are unreachable. Are there any mechanisms for being able to clear this and run pulumi up?
I’d be willing to manually go in and delete all the infra by hand, but want to ensure when
pulumi upb
billowy-army-68599
07/08/2022, 1:56 AM
You must be on an old provider version, you'll have to manually remove the resources in which case
m
magnificent-helicopter-3467
07/08/2022, 2:00 AMRight, I’ll do that on the infra side. But how do I clear the pulumi state for the stack? After I delete the infra, if I run
pulumi upb
billowy-army-68599
07/08/2022, 2:27 AM
you'll need to
pulumi stack exportpulumi stack import --filebillowy-army-68599
07/08/2022, 2:27 AM
or if you have the urns, you can do
pulumi state delete <urn>m
magnificent-helicopter-3467
07/08/2022, 7:39 AMexport --> import probably would have done the trick. Didn’t let me delete urns since it claimed they didn’t exist. Ended up deleting the stack and redeploying.
514 Views