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 - specifying `metadata.name` explicitly (as you would in YAML) will let you provide a specific physical name for the namespace. 

<@UB3BGTV63> Thanks, finally I got it with `ns = Namespace("rook-ceph", metadata={"name": "rook-ceph"})`

But now my `pulumi up` only creates the namespace and chart doesn't seem to do anything :disappointed:


```+ pulumi:pulumi:Stack: (create)
    [urn=urn:pulumi:lab-dev::shadowkeep::pulumi:pulumi:Stack::shadowkeep-lab-dev]
    + kubernetes:<http://helm.sh/v2:Chart|helm.sh/v2:Chart>: (create)
        [urn=urn:pulumi:lab-dev::shadowkeep::kubernetes:<http://helm.sh/v2:Chart::rook-ceph|helm.sh/v2:Chart::rook-ceph>]
    + kubernetes:core/v1:Namespace: (create)
        [urn=urn:pulumi:lab-dev::shadowkeep::kubernetes:core/v1:Namespace::rook-ceph]
        [provider=urn:pulumi:lab-dev::shadowkeep::pulumi:providers:kubernetes::default_1_3_1::04da6b54-80e4-46f7-96ec-b56ff0331ba9]
        apiVersion: "v1"
        kind      : "Namespace"
        metadata  : {
            labels: {
                <http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>: "pulumi"
            }
            name  : "rook-ceph"
        }```

Well well, somehow my Helm repo was lost, would've been nice if Pulumi told me so:

```$ helm template rook-release/rook-ceph
Error: failed to download "rook-release/rook-ceph" (hint: running `helm repo update` may help)```

Helm repo was missing since Snap has updated my Helm to version 3 at some point, now as I rolled back to version 2 it works.

Did Pulumi not report any error?  It definitely should report back the failure of the `helm template` command. If you can reproduce it not doing so - please do open an issue. 

I was just getting logs of this case when I noticed that I had `sys.exit(0)` in the main script, removing that caused Pulumi to report issues with the chart :slightly_smiling_face: