This message was deleted.

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.