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

There's a `transformations` option you can pass on a `new Chart` in Pulumi to get a chance to modify any of the resources created by the Helm chart prior to deploying them with Pulumi.

It's a bit of a blunt hammer, but useful for exactly this sort of scenario. See <https://pulumi.io/reference/pkg/nodejs/@pulumi/kubernetes/v2/#BaseChartOpts-transformations>.

The other alternative - common in the Helm world - would be forking the chart to expose this option.

We don’t want to fork because it is istio’s base chart.

FYI, here's an example where we're using transformations to change the namespace and edit the Services in an upstream helm chart: <https://github.com/pulumi/pulumi-kubernetes/blob/e4fa04b13a20929c879aca1bbe58fb5a95d16f7c/examples/helm/index.ts#L34-L52>