https://pulumi.com logo
#general
Title
# general
f

freezing-quill-32178

07/22/2021, 9:28 AM
Hello everyone, Is someone having issues with the latest 2 versions of Pulumi in general working with
Helm
and
pulumi.StackReference
, particularly slow
pulumi up
… for example stack that usually took ~2 mins now take 5+ 10, some Helm stacks never finish so had to be killed as well (which lost the actual stack.json state and had to be recreated from backup and cleaned up) The Helm resources are marked as deleted (and actually deleted on the k8s cluster) but the
pulumi up
is stuck and never finishes), inspecting the stack json the resources are still present in the
pending_operations
. I’m using
cert-manager
helm chart for example, failed during install and during uninstall as well Also seeing a lot of
Copy code
I0722 11:14:27.696360   74884 request.go:655] Throttling request took 1.07776852s, request: GET:https://[REDACTED]/apis/flowcontrol.apiserver.k8s.io/v1beta1?timeout=32s
    I0722 11:14:38.496586   74884 request.go:655] Throttling request took 1.098435921s, request: GET:https://[REDACTED]/apis/admissionregistration.k8s.io/v1?timeout=32s
For example the last
pulumi up
installing
cert-manager
v1.4.0 through the helm chart took 45 minutes.
b

billowy-army-68599

07/22/2021, 5:11 PM
could you open an issue with a repro in github.com/pulumi/pulumi-kubernetes for this
f

freezing-quill-32178

07/22/2021, 6:55 PM
@billowy-army-68599 for sure tomorrow, I just want to see what is happening with
TF_LOG=TRACE pulumi up --logtostderr -v=9
for better description
8 Views