Open piclemx opened 4 years ago
Thanks for the feedback! Just to make sure I understand, are you suggesting that we should be able to take a Helm chart and have it codegen the resulting Pulumi code? It'd be great to understand what about the existing Helm support doesn't meet your needs? https://www.pulumi.com/docs/guides/adopting/from_kubernetes/#deploying-helm-charts
Are you looking to import a chart as a starting point, but then take over from there?
Yeah. You understand me right 😄 .
I prefer doing some code to do so. I think for pulumi to be more successful that comes with creating some repos or stuff like that to deploy key component inside k8s.
Example. I will prefer to deploy prometheus with pulumi without do it with the helm chart. It will be great to have something like.
pulumi/pulumi-prometheus
so It will contains an import for the chart and after that this could be a shared lib for everyone.
What do you think?
I can definitely see the use case. How would you want to deal with updates to the chart itself? Do you expect that to work at all and if so, how? In the case of no changes, I could see a way for that to potentially work. But let's say you've changed the shared library after your import -- do you still want to be able to get chart updates incorporated in or are you okay with being "on your own" at that point?
I think being on your own as a start will be enough. But If we can keep both up to date together it will be awesome also. The first one will give more advantage to used pulumi or migrate to pulumi.
It will be a kickass feature to be able to give Pulumi an helm chart and Pulumi can create the ressources that the chart will have been created but in programatic way.
If you took something like this chart https://hub.helm.sh/charts/stable/fluent-bit.
This could create the project that will create this in the runtime of your choice.