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

Maybe the section on *Outputs* will be helpful here <https://pulumi.io/reference/programming-model.html#output>

<@UGD8LK61H> our behavior here is precisely the same as Kubernetes. The `.metadata.ownerReference` will be set for supported versions of the API server.

Can I use the output of a resource, from inside that resource? :thinking_face:

OK <@UBAJ7TD53>, maybe its just a bug in the tectonic pod filtering. It definitely gets the count right on one page but the list of pods on the other page shows me everything that matches the label selector

cc <@UEE5CDE2D> who worked at CoreOS, I’m actually not sure of their behavior here.

It seems like a strange thing to put in the labels, though, since there is a dedicated field for this.

the pod count probably comes from the deployment itself.

fair, i think i am succumbing to a tectonic ui bug more than anything else at this point.

i *think* it might be nice to have the stack name in my resource names? i am not 100% sure here either. I know the hashes keep things from colliding but if i have a bunch of people with stacks deployed, it may become chaos

that’s reasonable, that actually seems liek a good fit for labels though

actually having the stack name may be needed in those label selectors to prevent two different stacks from getting picked up in the same service

<@UGD8LK61H> you’re in good hands with <@UBAJ7TD53> :slightly_smiling_face:

I personally use a prefix for all my resources. I defined the prefix in my pulumi config

sometimes people predictable prefixes, but this is more common in AWS where there aren’t namespaces.

let me think for a second about the labels referencing the name though…

this is an interesting use case that I don’t think we have super good support for.

we shove product codes into our names in AWS, i was even thinking we may need some kind of policy enforcing module

<@UFMD9FETZ> the prefix is a good idea. is that something you are manually prepending to all names or is there some special variable?

basically for some

```
const foo = new Deployment("...", { ... })
```

somehow you’d need to get `foo.metadata.name` into the labels of the second argument, which is semantically strange, because `foo.metadata.name` is basically a `Promise&lt;string&gt;` that is computed after the resource has finished initializing.

i kind of had that problem getting the name of a configmap into a volume

not really, pulumi adds the suffix, but we have no way to do this sort of multi-step passing of computed fields around in our model.

```              name: envoyConfigMap.id.apply(function(t) {
                return t.split("/")[1];
              })
```

Yes, I manually prepend the prefix to all my resource names

we’re working on that sort of thing, btw