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

Also, the example I found is using helm chart to install istio which will be deprecated in the future. The recommended approach is to use the `istioctl` client, but how does that work with pulumi? Do you know <@UB39JFCKC> 

<https://pulumi-community.slack.com/archives/CRFURDVQB/p1582219961137100?thread_ts=1582156689.134500&amp;cid=CRFURDVQB>

Got it, so basically not using istioctl to manage kubernetes, just to generate the manifests needed. 

Sounds doable. A lot of new things for me, but a great learning experience :) 

Yep, that’s my suggestion. You could also shell out to `istioctl` from Pulumi to generate the manifests as part of an update if that process is working out for you. A little clunky, but I think the advantages of managing resource updates with Pulumi are worth it.

(That’s very similar to the way we integrate with Helm)

For reference, here is the Helm wrapper: <https://github.com/pulumi/pulumi-kubernetes/blob/master/sdk/dotnet/Helm/ChartBase.cs#L95-L122>