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 currently deploy a chart like
```Chart("some-name,config=LocalChartOpts(path=path/to/helm-chart,ns=...,values=custom_values))```

You can specify a version of the chart:
<https://www.pulumi.com/docs/reference/pkg/kubernetes/helm/v3/chart/#version_nodejs>

If I'm specifying a path to the chart, I'd assume it's getting the version by definiton. What I was wondering is there an equivilant to `helm upgrade` or does it intuit the change by the change of values. I guess I need to look at the helm source and look further into the pulumi source to understand

we don't use  any of helm's server side logic, pulumi essentially runs `helm template` with the chart and then renders the output and looks through the yaml list and applies each of the resources. If you're using a local chart, and you update the local chart source, `pulumi up` will just run `helm template` again.