Recommendation for container naming convention

[JBBianchi]

What would you like to be added?

I propose adding a recommendation to the Serverless Workflow specification for runtime implementers for naming containers when executing run tasks of type container.

Proposal(s):

When a run task of type container is executed, the container name should follow a clear, predictable naming convention.

For example:
{workflow-instance-id}-{task-name}

• workflow-instance-id: Ensures the name is unique to the workflow instance.
• task-name: Identifies the specific task being executed.

Alternative(s):

No response

Additional info:

• A predictable container naming convention would align with best practices for workflows executed in distributed systems.
• This feature would not impose hard constraints but serve as a guideline for runtime implementations.
• Use cases include monitoring, logging, and container lifecycle management, where a standardized name can greatly simplify troubleshooting and system understanding.

Community Notes

• Please vote by adding a 👍 reaction to the feature to help us prioritize.
• If you are interested to work on this feature, please leave a comment.