Repository navigation
Add another specialization for run: job or k8s-job #1300
Description
Activity
- changed the title
[-]Add another speficalization for run: job or k8s-job[/-][+]Add another specialization for run: job or k8s-job[/+]on Apr 12, 2026 Im not sure if this one belongs here or should be opened on the specification repo here https://github.com/serverlessworkflow/specification/tree/main
You are right that container is asuming docker or podman is installed on the host running the orchestration application and I think we need some way on the specification in order to make the distinction you are looking for when the workflow is writtenMy bad, you did not ask for a different idiom in the specification, but a different runner for container (we only have docker right now), certainly we can add a new one.
What would you like to be added:
Currently, the spec includes
run:container, which I inferred requires a Docker or Podman client installed on the host where the orchestration application is running.But there is another scenario: The image may be run as a Kubernetes/Openshift Job in a cluster.
Why is this needed:
Many companies uses ephemeral Kubernetes Jobs to do batch processing.