Run
Run deploys container images as services or finite jobs within a Project. It manages runtime configuration, deployment history, and the URLs that make services reachable.
Why use Run?
An image needs a runtime, configuration, and a way to release changes. Run brings those operations together around a stable Workload, so you can deploy a new image, inspect its health, and return to a previous successful Revision.
What you can do
- Deploy local source through Build, or deploy an existing OCI image.
- Configure environment variables and bind Project-owned Secrets.
- Inspect deployment status, logs, and lifecycle events.
- Roll back to an immutable Revision and connect custom hostnames to services.
Core concepts
A Workload is one runnable service or job and its desired configuration. A Deployment is an attempt to apply an image and configuration. A successful Deployment creates a Revision containing the exact image and runtime settings, including resolved Secret versions.
Service Workloads have URLs. A Route connects a custom Hostname to a service Workload; Domain owns the Hostname claim. Job Workloads run finite tasks without a service URL.
Use Run
Read the CLI reference for commands or the API reference for resources, request fields, and responses.