Oh, I just went from tsconfig explicit files to include/exclude. let me try that.

Switching back to

files

in

tsconfig.json

didn’t help. My project contains several typescript files (all for pulumi), one typings folder with manually added type definitions for one library that didn’t support typings and the node_modules folder of course. That setup was the same for months.

Switched back to node@13 instead of node@10 which I still had pinned due to some earlier incompatibilities I had. Same behaviour.

I don’t get it what causes this issue. Inspecting the log even shows that the

StackReference

was already resolved - I can see some content from the given stack (e.g. the exported kubeconfig) and some kubernetes resources using this resource that are diffed (and found to be same).

I was able to track down the problem but still no clue how to solve it. If I remove the new resources from my script - basically ending up with a zero-changes diff then everything works. If I on the other hand add the resources (just one kubernetes

ConfigFile

) I end up with a never halting process. The resources don’t use anything from the

StackReference

as I’m just migrating to a self-contained pulumi project without stack references but I planned some soft migration with two clusters instead of tearing down one and creating a new one later.

The thing I want to deploy is https://github.com/jetstack/cert-manager/releases/download/v0.13.0/cert-manager.yaml using

kubernetes.ConigFile

which has loads of resources. But I already did that with v0.11.0 before which was basically the same size.

I cannot imagine diffing of some 30-50 kubernetes manifests can take so long.

I faced the issue when trying to update cert-manager as well.

I’ll try upgrading later.

Thanks @rapid-eye-32575. You were perfectly right. The issue is gone after upgrading

@pulumi/kubernetes

from

1.4.5

to

1.5.1

. 🎖️