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 will ultimately need to have unique names - so something morally Luke `resourcePrefix` will be necessary. 

Where exactly do you hit the name limit - and are you in control of all parts of that name?  Ideally the resource prefix would only need to be used for the Pulumi logical name - and wouldn’t need to be passed to Helm at all.

I am in full control of the name, and have managed to figure out a workaround using `resourcePrefix` and shortening what I was feeding in.

I was actually compounding the problem initially because `resourcePrefix` gets prepended to the `name` given to the Chart resource, and thus gets very long very quickly.  As those are fed directly to the `--name-template` arg it's very easy to hit the 53 char limit.

Fortunately the charts in question all support a `fullnameOverride` value, so I've been able to utilize that to rename the resources as they appear in the cluster without resorting to more complicated transformations.