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

here's what I'm looking at <https://pulumi.io/reference/pkg/nodejs/@pulumi/kubernetes/v2/#ChartOpts>

I think you're running into <https://github.com/pulumi/pulumi-kubernetes/issues/217>

You should be able to use a transformation to work around that. See <https://github.com/pulumi/pulumi-kubernetes/blob/master/tests/integration/yaml-url/step1/index.ts#L20-L34>

hmm ill give it a shot. thanks a bunch for the help!

<https://github.com/pulumi/pulumi-kubernetes/issues/217#issuecomment-459105809>

<@UF7LGS5T3> we’re basically semantically equivalent to `helm template`, btw. Not sure if we should change this — helm is moving away from Tiller, so in the medium term these charts will need to support this too.

in the provided example, can I pass in a param to `addNamespace` so that we can reuse that function?

i think i'm missing something with `transformations`

i'm trying `transformations: [addNamespace("kube-system")]`

and added it into the method signature ```161 function addNamespace(o: any, namespace: string) {
162     if (o !== undefined) {
163         if (o.metadata !== undefined) {
164             o.metadata.namespace = namespace;
165         } else {
166             o.metadata = {namespace: namespace}
167         }
168     }
169 }```

bug on my side :face_palm:  will work it out

<@UF7LGS5T3> just got back from a meeting, sorry.

haven't worked it out quite yet but have an idea on how to do it