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

Yes, we use a transformation to handle it.

```
new k8s.helm.v2.Chart(config.project, {
  chart: 'stable/jenkins',
  version: '1.3.3',
  namespace: namespace.metadata.name,
  values: {
    master: {
      serviceType: 'ClusterIP',
    }
  },
  transformations: [
    (resource: any) =&gt; {
      resource.metadata.namespace = namespace.metadata.name;

      // This fixes the test failing
      if (resource.kind == 'Pod') {
        resource.metadata.annotations = {
          '<http://sidecar.istio.io/inject|sidecar.istio.io/inject>': 'false'
        };
      }
    }
  ]
});
```

I’m a bit wary of that, in case a chart uses non-cluster-scoped resources

It hasn’t seemed to have broken anything for us, but I get your worry. I think there are some other more complicated transformations that do the same thing, but ignore those types of resources

It’s the only solution that I am aware of.

The proper solution though is to submit a PR against the chart and have them add the namespace explicitly.

Tiller is going away, so they will need it anyways I believe. I’ve seen several charts accept these changes.

ok, cheers -  I don’t get why setting the namespace on the k8s provider doesn’t work though :thinking_face:

<@UM4RJMTFS> Would you mind filing an issue with details on the provider namespace not working for you? <https://github.com/pulumi/pulumi-kubernetes/issues/new>

done: <https://github.com/pulumi/pulumi-kubernetes/issues/754>

Updated the ticket with a resolution. This chart was already fixed upstream, so you just have to set the `namespace` parameter on the chart to get the behavior you want

Yep just saw - that’s a fix for this specific chart, but I’d guess that there’s a general issue with Helm not respecting the k8s provider’s namespace?

Right. We don’t use Tiller, so some charts don’t work out of the box. Best thing is to fix the chart upstream, but the other ways can be used to work around in the meantime

To clarify, the provider namespace flag is a default, not an override, so the chart’s value was taking precedence here

fair enough - I know it’s not Pulumi’s doing, but this is pretty hard to work with at the moment. The workarounds detailed here don’t always work for all Helm charts <https://github.com/pulumi/pulumi-kubernetes/issues/217#issuecomment-504160101>

If you find specific cases that are confusing, please open an issue. We’re trying to make it as easy as possible, but it’s hard given the variety of approaches taken by helm charts

Since Tiller is going away with Helm 3, I’d expect the namespace issue to get better over time