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'm a k8s newbie, apologies for incorrect terminologies. I'm trying v4 charts, installing airbyte/airbyte. The _only_ Kubernetes resource I'm currently using is the Chart.
I've figured out that I can't use `chart: 'airbyte/airbyte'`. I'm trying `namespace: 'airbyte', chart: 'airbyte'` and that's getting further. However I'm now getting a pile of errors including this text:
&gt;  ...was not successfully created by the Kubernetes API server: namespaces "airbyte" not found
Searching says I should add the `create namespace` property but that's not in the Chart resource.
How do I get the chart installed? Can I configure something to automatically create namespaces for me?

Or should I create the namespace in my cluster before declaring the Chart? I have found a resource type kubernetes.core/v1.Namespace. I'll try adding one of those before my Chart.

Yes this seems to be working. It's been creating resources for a while now, without errors. In case someone else finds this thread looking for the same solution, it was as simple as
```new k8s.core.v1.Namespace('name', {
  metadata: {
    name: 'airbyte'
  }
}, { provider });```

Only <https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v3/release/> has the "create_namespace" option. Using `Release` with the option set to true is the equivalent to calling `helm install --create-namespace ...` . Pulumi will handle the `Release` as one resource.

With the `Chart` , you get access to all the Kubernetes components the Helm chart defines within Pulumi. Roughly speaking, `Chart` treats the Helm chart as a component resource definition, rather than being a wrapper for `helm install` . It supports fewer Helm features, but gives you more direct insight and control.

If you're just installing a Helm chart, you're probably better off using `Release` . I recommend reading <https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/choosing-the-right-helm-resource-for-your-use-case/> for a very thorough discussion and guide on when to choose which option.

Awesome insight. That's a great help for a newbie. I shall change to using Release on Monday. 
I guess there's no v4 Release? I just use the v3 one?

Hmm, <https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v4/chart/|looks like it's in the works:>
&gt; _Looking for the Release resource? Please use the <https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v3/release/|v3 package> for production use cases, and stay tuned for an updated Release resource, coming soon._
&gt; _See also: <https://www.pulumi.com/blog/kubernetes-chart-v4/|New: Helm Chart v4 resource with new features and languages>_
(Also, very happy to be able to help you a bit for a change, after learning so much from your comments on this Slack.)

Update from Monday morning: the v3 Release just worked. Stress levels through the floor. Happiness all around. End of story.

Thanks <@U06ET49CBFA> for the guidance, and happy to hear about the good result, <@U012UJTT55M>