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

Quick question here - according to the Kubernetes NodeJS doc, when I create a new deployment using `new k8s.apps.v1.Deployment(name: "some-name")`,  shouldn't `some-name` become the resource name? Why does it become appended by a random string?

if you set the name property in the metadata block it will respect it but you have to check for uniqueness yourself after that

Autonaming allows us to improve the replacement semantics of kubernetes resources. So for example, if a config map's data is updated, pulumi can create a new config map, then update all pods to use the new version, and then only if that succeeds, delete the old one. 

Kubectl, in contrast, will simply update the data in place which does NOT trigger a rollout among deployments that reference it. 

So overall, this is actually a huge win. 