hallowed-ghost-37140
11/10/2023, 3:02 PMindex.ts
one-by-one by commenting them out and running pulumi up
.
Then after the resource was removed I'd re-attempt to run pulumi destroy --exclude-protected
to see if the grpc: the client connection is closing
issue had gone.
I found that once I'd deleted all the Helm release resources, and finally commented out the kubernetes.Provider
created from the kubeconfig
obtained from the DigitalOcean cluster resource.
export const kubeconfig = doCluster.kubeConfigs[0].rawConfig;
// v HI IT'S ME
const provider = new kubernetes.Provider("k8s-provider", {
kubeconfig,
});
// ^ I'M THE PROBLEM IT'S ME!
const ingressNginxNamespace = new kubernetes.core.v1.Namespace(
"ingress-nginx-namespace",
{
metadata: {
name: "ingress-nginx",
},
},
{
provider,
}
);
The issue finally went away.
node ➜ /workspaces/evilapp/infrastructure (main) $ pulumi destroy --exclude-protected
Previewing destroy (dev)
View in Browser (Ctrl+O): <https://app.pulumi.com/evilcorp/evilapp/dev/previews/c5700262-a76c-441d-a4ac-7d02469a5397>
Type Name Plan
pulumi:pulumi:Stack evilapp-dev
- ├─ digitalocean:index:Project do-project delete
- └─ digitalocean:index:KubernetesCluster do-cluster delete
Resources:
- 2 to delete
Do you want to perform this destroy? details
- digitalocean:index/project:Project: (delete)
[id=d43c405f-df9f-4c34-aa34-ec1c69c329e9]
[urn=urn:pulumi:dev::evilapp::digitalocean:index/project:Project::do-project]
[provider=urn:pulumi:dev::evilapp::pulumi:providers:digitalocean::default_4_23_0::1b8a542e-e825-441c-9c95-f928fa347bee]
- digitalocean:index/kubernetesCluster:KubernetesCluster: (delete)
[id=08c8c8a4-50a6-462c-9683-84e1e78fef0b]
[urn=urn:pulumi:dev::evilapp::digitalocean:index/kubernetesCluster:KubernetesCluster::do-cluster]
Any ideas why the kubernetes provider is causing this issue when performing a destroy.