sparse-intern-71089
07/20/2023, 1:36 PMsalmon-account-74572
07/20/2023, 2:46 PMPULUMI_K8S_DELETE_UNREACHABLE
to true and re-run your commands, but be aware that will remove resources from your Pulumi state. The only other fix is to correct whatever problem is preventing Pulumi from being able to contact the specified Kubernetes cluster. Maybe you’re using the default Kubernetes provider and your local Kubeconfig isn’t correct?mammoth-caravan-43791
07/21/2023, 2:45 AMsalmon-account-74572
07/21/2023, 3:18 PMmammoth-caravan-43791
07/21/2023, 5:48 PMPULUMI_K8S_DELETE_UNREACHABLE=true pulumi destroy
though I can see the messages error: configured Kubernetes cluster is unreachable: unable to load schema information from the API server: ...
and If the cluster has been deleted, you can edit the pulumi state to remove this resource
salmon-account-74572
07/21/2023, 5:49 PMPULUMI_K8S_DELETE_UNREACHABLE=true pulumi refresh
to see if that cleans up the dangling Kubernetes resources.mammoth-caravan-43791
07/21/2023, 5:56 PMerror: Preview failed: failed to read resource state due to unreachable cluster. If the cluster has been deleted, you can edit the pulumi state to remove this resource
due to unreachable cluster. And there are too many resources to delete manually.salmon-account-74572
07/21/2023, 7:08 PMdeleteUnreachable
provider configuration option) should help with this issue. If it isn’t, then there may be more going on here.mammoth-caravan-43791
07/24/2023, 1:37 PM