Docker, Kubernetes & Cloud Task Runners Explained

For the complete documentation index, see llms.txt. For a full content snapshot, see llms-full.txt. Append .md to any kestra.io/docs/* URL for plain Markdown.

Choose a task runner to control where and how Kestra executes your script tasks.

Task runnerEditionDescription
ProcessOSSRuns tasks as local processes on the Kestra worker
DockerOSSRuns tasks in Docker containers (default)
KubernetesEERuns tasks as Kubernetes pods
AWS BatchEERuns tasks on AWS Batch (ECS Fargate, EC2, or EKS)
AWS EC2EERuns tasks natively on EC2 instances via SSM — for GPU workloads, licensed software, and Spot instances
Azure BatchEERuns tasks on Azure Batch containers
Azure Virtual MachineEERuns tasks natively on Azure VMs via the Run Command API — no SSH, no container
Google BatchEERuns tasks on Google Cloud Batch VMs
Google Cloud RunEERuns tasks as serverless Google Cloud Run jobs

Process and Docker are open-source and built into Kestra. Cloud-based runners require an Enterprise Edition license.

Was this page helpful?