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 can pass the name explicitly through the metadata object, as per standard kubernetes convention

Hey! HNY! :slightly_smiling_face:
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 :slightly_smiling_face:

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

It's probably best to pass service dns names in via environment variables btw, that way you can take advantage of the auto naming

Main one being to reduce downtime in the event an object/resource needs replacing

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?

If everything is contained within the same pulumi stack, use auto-naming as you can pass by reference.
Otherwise use static names for the service