What is the semantic meaning of the metadata.name field?

[sameerajayasoma]

Hello Score community,

The Score spec says that it is a string that can describe the workload, but how is it used when generating K8s artifacts? What happens if this name changes in subsequent updates? I'm sorry if this has been talked about before.

Thanks.

[mathieu-benoit]

Hi @sameerajayasoma, thanks for reaching out.

I confirm that for both score-compose and score-k8s implementations, updating the metadata.name field in the Score file after a previous generate will append the new name as another workload in the state.yaml file as well as in the generated compose.yaml and manifests.yaml. So typically, not removing the previous one, and landing to duplicating workloads/manifests.

Wondering if it's a bug or if --prune (or something) would be a good feature request candidate here?

@astromechza, any thoughts here?

[astromechza]

Yup, the name is the identity of the workload. If you redeploy it with a new name it's seen as a new workload and the previous workload will remain running even if it is the same.

Then you can manually undeploy the old workload.