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

I might try to use that for rendering 10+ helm charts and using the YML in pulumi , instead of the helm chart resource.

Helm charts add quite a bit of time to `preview/update`

The Helm implementation uses the YAML support under the hood, so I wouldn’t expect that to improve performance if you’re still deploying the resources with Pulumi. That said, if you have particular charts that seem to perform poorly, you can file an issue so we can investigate further.

<@UD2HJDBCL> I filed an issue to cache helm chart rendering work. This should make things more efficient under the hood. See <https://github.com/pulumi/pulumi-kubernetes/issues/935>

That looks promising.

For us it's `traefik`, `cert-manager`, `kiam`, `external-dns`, `datadog`, `cluster-autoscaler` templated for 5 clusters (30 charts total in the stack). It takes around 2m30s to run to completion making the whole process take 5mins per iteration.