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

Can you elaborate? Namespace created by pulumi, or out of band?

Either, but for a namespace created by pulumi, can I _later_ label it, or does the labeling have to be declared at creation time?

The properties are set when you instantiate the resource and run an update. However, you could change the labels later and then run another update. Not sure if that answers your question. Did you have a specific use case in mind?

<@UE1LN7A22> ah, okay, I'm thinking that we might want to manage a label on a namespace as its own "resource", because certain cross-cutting infrastructure jobs might make requirements

e.g.: for a networkpolicy for the `app` namespace, we need to label the `nginx-ingress` namespace, like so:

```
apiVersion: <http://networking.k8s.io/v1|networking.k8s.io/v1>
kind: NetworkPolicy
metadata:
  name: foo
spec:
  podSelector:
    matchLabels:
      app: foolts
      release: {{ .Release.Name }}
  ingress:
  - from:
    - namespaceSelector:
        matchLabels:
          name: foo-nginx-ingress
```

The namespace might have _other_ labels, but it *needs* the `foo-nginx-ingress`. So it might be nice to be able to say, "Hey, this namespace needs a label", without affecting anything other labels already on it. Effectively a "label set membership" resource.