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

you have to place that under `metadata` (gimme me a sec)

Yeah are you able to provide an example as I can see that in the docs but can't figure out the syntax. I am not a python developer unfortunately

```import pulumi_kubernetes as pulumi_k8s

monitor_namespace = pulumi_k8s.core.v1.Namespace(
  "snyk-monitor",
  metadata=pulumi_k8s.meta.v1.ObjectMetaArgs(
    name="snyk-monitor",
  ),
)```

you can put simple dict instead of `pulumi_k8s.meta.v1.ObjectMetaArgs` but I like my things “strongly typed” wherever possible :slightly_smiling_face:
```monitor_namespace = pulumi_k8s.core.v1.Namespace(
  "snyk-monitor",
  metadata={
    "name": "snyk-monitor",
  },
)```

If you wonder why I don’t have `resource_name` as in your example, that’s because it’s the first argument in all pulumi resources so you can pass it as positional argument (first one) or as key-value as you did.

Yep I just had the syntax wrong. Thanks so much <@U0288KYUB7C> it's clear now it will work for me

```+ pulumi:pulumi:Stack: (create)
    [urn=urn:pulumi:dev::gcp-K8s-integration-demo::pulumi:pulumi:Stack::gcp-K8s-integration-demo-dev]
    + kubernetes:core/v1:Namespace: (create)
        [urn=urn:pulumi:dev::gcp-K8s-integration-demo::kubernetes:core/v1:Namespace::snyk-monitor]
        [provider=urn:pulumi:dev::gcp-K8s-integration-demo::pulumi:providers:kubernetes::default_3_13_0::04da6b54-80e4-46f7-96ec-b56ff0331ba9]
        apiVersion: "v1"
        kind      : "Namespace"
        metadata  : {
            labels: {
                <http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>: "pulumi"
            }
            name  : "snyk-monitor"
        }```