Hello! Question on resource names. "Before pulumi" If you wish a deployment D to talk to a service S you simply give S a name "my-srv" in a yaml and configure D to find S by that very DNS name "my-srv". Now with pulumi there's auto-naming (probably for good reasons) and a service gets a DNS name with a suffix that is not known to client deployments before creating the service. The best I can think of is disabling auto-naming for kubernetes services. But what's the idiomatic way in pulumi for a deployment to discover a service?

You can pass the name explicitly through the metadata object, as per standard kubernetes convention

Hey! HNY! 🙂 thanks for reply! yeah, this does the trick but auto-naming was not introduced without a reason and I wondered when pulumi decided to give services random names, what was their plan about it 🙂

As far as I know, auto-naming has always been a thing

so within pulumi context I first deploy a service, obtain it's name and pass this name when deploying further deployments that are supposed to talk to this service?

Are you setting up Deployments outside of pulumi?

ok, thank you for suggestions!