No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Does `helm.v3.Release` support `kubernetes:renderYamlToDirectory` like `helm.v3.Chart`?

<@UDWGK72BY> Any ideas on how best to proceed with getting k8s manifests from `helm.v3.Release`?

Because of how `Release` is designed, it simply doesn't interoperate with `renderYamlToDirectory`.

I would be curious to hear more about your use case for `renderYamlToDirectory`.

<@U05QU9RNUN9> I built an argocd-pulumi plugin that is working pretty well.

Why is it preferable to apply the manifests using Argo?

ArgoCD has an amazing UX for devs, really robust rbac and sso integration, abstracts away kubectl for those who don't want to use it. It adds a lot of value and integrates with tooling I use.

Pulumi has been a nice bridge between my static infra and gitops pipelines that are both managed with pulumi.

And the plugin uses `renderYamlToDirectory` such that Argo applies the manifests?  Is it possible for the plugin to let Pulumi apply the manifests in the ordinary way?

No unfortunately. An argocd plugin just produces manifests to pass via grpc to the argocd repo server.

Thanks.
Will `Chart` work for you, given that you pre-configure the registry credentials?

Yeah it's been a couple days, and I've moved on to other tire fires but I feel like this unblocked me with Chart: <https://pulumi-community.slack.com/archives/CRFURDVQB/p1712957085668039?thread_ts=1712948195.195679&amp;cid=CRFURDVQB>

I just call that at the beginning of the template generate invocation.