Running Aggrelis in your own cluster takes fewer extra steps, and the defaults are harder to get wrong.
- Both consoles from the Helm chart, with health checks, disruption budgets, network policies and an optional ingress, turned on with one value.
- Encryption in transit, or no start. In production the engine starts only when each listener has a certificate or you state that a TLS proxy sits in front of it.
- Tighter network defaults: the operator console is reachable only from the peers you name, and metrics only from your monitoring namespace.
- Hardened containers for Docker Compose, with fixed addresses, health checks, resource limits and security headers on every response.