Deploying with Kubernetes
Agent Mesh is deployed on Kubernetes using a Helm chart. Three deployment paths are available depending on your use case.
| Path | Use case | External dependencies |
|---|---|---|
| Kubernetes Quick Start | Evaluation and proof of concept | None—event broker and storage are embedded |
| Installing Kubernetes for Production | Team and production deployments | External event broker, Postgres, and artifact storage required |
| Installing in an Air-Gapped Environment | Disconnected or restricted network environments | Same as production, but all dependencies must be accessible within the air-gapped network; private image registry also required |
The Quick Start is not suitable for production use. It embeds a development event broker and ephemeral storage that are not supported for workloads serving real traffic.
For CPU and memory sizing guidance for production Kubernetes deployments, see Compute Resources.
To run workloads under a sandboxed container runtime such as gVisor or Kata Containers, see Sandbox Pod Runtimes.
For prerequisites that apply to all Kubernetes deployments, see Before You Begin.