Container execution: Each workflow step runs in its own Docker container with specific tools and dependencies.Coordination: Kubiya’s platform manages workflow scheduling, step dependencies, and data flow between steps.State management: Step outputs are captured and passed to dependent steps automatically.Resource management: Containers are created, executed, and cleaned up automatically.
Isolation: Each step runs independently - no conflicts or shared state issues.Flexibility: Use any Docker image, language, or tool you need.Reliability: Same inputs always produce same outputs.Scalability: System scales automatically based on workload.Clean execution: Fresh environment for every step prevents drift and issues.
Step outputs: Each step can produce outputs that become available to dependent steps.Environment variables: Outputs are passed as environment variables to next steps.File artifacts: Steps can also share files through mounted volumes when needed.No shared state: Steps cannot interfere with each other’s execution environment.
Step failures: Failed steps can be retried with configurable backoff strategies.Partial execution: Only affected steps need to re-run, not the entire workflow.Resource limits: Steps have CPU, memory, and time limits to prevent runaway processes.Clean recovery: Failed containers are removed and fresh ones created for retries.
Define steps: Specify what containers and commands each step needsSet dependencies: Tell Kubiya which steps depend on othersHandle outputs: Capture important data from steps for use in later stepsAdd error handling: Configure retries and timeouts for robust executionNext: See practical workflow examples or learn the DSL syntax