This message was deleted.
# general
s
This message was deleted.
s
if you set the name property in the metadata block it will respect it but you have to check for uniqueness yourself after that
c
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.