This message was deleted.
# kubernetes
s
This message was deleted.
d
Absolutely understand where you're coming from, I feel the same. I've found
Release
works fine most of the time for simpler charts, but they generally don't have hooks anyway. Using Release in those cases makes for a good cost-saving measure if you're using Pulumi Cloud. It's my experience with helm as a tool in general too, so I really don't blame pulumi for it. I actually had my CI do a retry when pulumi fails to work around the flakiness.
It's disappointing that the issue for hook support in Chart was closed with the
Release
object: https://github.com/pulumi/pulumi-kubernetes/issues/555
👍 1
q
same story here, we try not to use helm at all and that's even with helm 3+, previous versions were even worse
s
I am not and never have been a fan of Helm, and generally do my best to avoid it at all costs. (Speaking personally here, not on behalf of Pulumi.)
d
It's been a while since I looked into it, but it'd be technically possible to implement hooks + the lookup api into the Chart resource. Would provide a good balance of compatibility with Pulumi's superior support of... well, everything k8s 😆
👍 1
s
I would be okay with this if I didn't need helm in the interim before jumping into kustomize and flux.