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

That is pretty standard Pulumi behavior, but you can set a `name:` parameter to specify a name that won't get the ID appended

<https://www.pulumi.com/blog/infrastructure-as-code-resource-naming/>

to be clear, the reason for this is because if we need to replace the resource because you changed an immutable property (in the case of `Service`, `.spec.clusterIP` is one example), we will want to create a new service before replacing the old one.

if you don’t add the suffix you can’t do this.

even kubernetes does this under the covers for replicasets and pods when you use `Deployment`

You _could_ hard code them, but this is almost always worse than the alternatives