Installation overview
There's one Helm chart for the server (continuum-server) and one for the agent (continuum-agent), both already published and ready to install — nothing to build or publish yourself.
Already did the Quickstart? You have a working server. This section is for the two things that come after: making it reachable for real (not just from your own machine), and connecting your first cluster.
| I want to... | Go to |
|---|---|
| Get a server running as fast as possible, anywhere | Quickstart |
| Expose it properly on a cloud cluster, with a real DNS name | Production cluster |
| I already run my own reverse proxy (nginx, Traefik, Caddy...) | Already run your own reverse proxy? |
| Install the agent in a cluster and see it appear in the UI | Connecting a cluster |
| Understand why the agent port needs special treatment | Exposing the agent port |
The one thing worth understanding before you touch any of these: the server has two separate listeners, and they're exposed completely differently. The agent port (:8443) speaks mutual TLS gRPC and that handshake has to reach the pod untouched — it can never be terminated at an HTTP proxy or Gateway. The admin port (:8080, the UI and JSON API) is the opposite: plain HTTP inside the pod, meant to sit behind a Gateway that terminates TLS in front of it. Mixing these up is the single most common way to get a confusing, half-working install — see Architecture for the full picture.