No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

How can I find on what `pulumi` is hanging/waiting during a `preview` (or the preview part of `up`)? This started happening since I deployed `cert-manager` v0.16.1 on a k8s 1.15 cluster.

Verbose and debug logging would be the first thing to try - `-v9 --logtostderr --debug`.

Wow… the flood of messages is crashing the terminal inside VSCode…

Can try a lower verbosity level first then, hehe. `-v5`

Since your arguments specify logging to `stderr`, I can redirect to file with `2&gt; pulumi.txt` right?

<@UDEJ1F5SQ> wont’t know exactly what to look for now. Log file is 107886 lines.

Update: although my package.json pointed to `@pulumi/kubernetes:2.3.0`, I still had an old 1.5.6 in my `node_modules` folder. Running `npm install` fixed that. When I preview now, it doesn’t hang anymore, but pulumi now wants to replace my full AKS cluster because it reports a change in `networkProfile`?!?!?!

After adding the `loadbalancerSku` to my AKS cluster, no changes anymore. It seems the default value was changed. Then, I bumped to `@pulumi/kubernetes:2.6.0` and the `hang` is gone… *sigh*