Workload recipes
Every workload on Kestrel fits one of three shapes. Pick the recipe that matches your workload’s lifetime, invocation pattern, and reachability needs — each one gives you tenant-scoped YAML, committed to your repo for ArgoCD to deploy (services, jobs) or applied directly with kubectl for throwaway dev pods.
Which recipe?
Section titled “Which recipe?”| If your workload… | Use this recipe |
|---|---|
| Runs continuously, serves traffic, needs an Ingress | Long-running service |
| Runs to completion once or on a schedule, then exits | Jobs & CronJobs |
| Is a short-lived interactive environment (e.g. Jupyter) | Dev pod |
Long-running service Deployment + Service + Ingress — the standard shape for web apps and APIs that run indefinitely.
Jobs & CronJobs One-shot batch processing and scheduled recurring work — data pipelines, nightly reports, cleanup tasks.
Dev pod Ephemeral interactive environments like JupyterLab — spin up, work, tear down.