I am fuming but not really. Actually this is fine, im having fun 😄 but seriously: https://github.com/pulumi/pulumi-kubernetes/issues/555 https://github.com/pulumi/pulumi-kubernetes/issues/1454 I know, entitled developer expects things to work. I never, even for a second, assumed that pulumi is not handling Helm transparently and it is in fact breaking charts that utilize hooks. And with all the upcoming k8s operator / controllers and CRDs more and more charts seem to be incorporating them. TL DR Pulumi cannot be used for Helm charts unless the chart is quite small and after every upgrade I can verify that no hooks are utilized.

thanks for the feedback, and sorry for the frustration 😞 We're having discussions about helm hooks and the helm support, we see the frustration here and are figuring out how to support going forward

@billowy-army-68599 im sorry for overreacting a bit, its late and I spent too much free time on this problem as I was really curious what it is (its not work when its fun, right 😄 ) 🙂 now that I know about this I would mostly wish for some warnings to be added in the docs (or there already are and I promptly missed them). And if supporting this Helm feature is still possible at some point that would be great ofc. But its probably a more complicated matter under the hood.

@red-lighter-44012 you could try and install via pulumi the helm-operator and deploy the helm-operator’s custom resources instead of using pulumi for deploying the charts I think the helm-operator should behave well with the helm hooks and that could solve your problem I’m considering doing this migration as well

@clever-byte-21551 thanks for the suggestion, I added it to my tasks for next week. I'm a bit behind schedule as this migration to traefik v2 turned out to be more painful than anticipated 😄 but I'll test it for sure.

I think you might be running into https://github.com/pulumi/pulumi-kubernetes/issues/1335 here, and I have a fix pending for this week’s release. Hopefully that will get you unblocked.