https://pulumi.com logo
#kubernetes
Title
# kubernetes
l

limited-rainbow-51650

09/11/2020, 2:38 PM
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.
g

gentle-diamond-70147

09/11/2020, 3:24 PM
Verbose and debug logging would be the first thing to try -
-v9 --logtostderr --debug
.
l

limited-rainbow-51650

09/11/2020, 3:31 PM
Wow… the flood of messages is crashing the terminal inside VSCode…
g

gentle-diamond-70147

09/11/2020, 3:32 PM
Can try a lower verbosity level first then, hehe.
-v5
l

limited-rainbow-51650

09/11/2020, 3:33 PM
Since your arguments specify logging to
stderr
, I can redirect to file with
2> pulumi.txt
right?
g

gentle-diamond-70147

09/11/2020, 3:36 PM
yes
l

limited-rainbow-51650

09/11/2020, 3:43 PM
@gentle-diamond-70147 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
4 Views