Kubernetes Deployment
The Kubernetes deployment of QuantumAPI uses Helm charts to deploy the full platform on any Kubernetes cluster. This provides production-grade features like auto-scaling, rolling updates, and high availability.
Choose Kubernetes when you need horizontal scaling, zero-downtime deployments, or integration with existing cluster infrastructure. For simpler setups, see the Docker Compose deployment guide.
Docker Compose vs Kubernetes
| Feature | Docker Compose | Kubernetes |
|---|---|---|
| Setup complexity | Low — single command | Medium — requires cluster |
| Horizontal scaling | Manual (limited) | Auto-scaling (HPA) |
| High availability | No (single host) | Yes (multi-replica) |
| Rollback | Script-based | Built-in (Helm) |
| Monitoring | Docker health checks | Probes + Prometheus |
| Best for | Dev, testing, small prod | Enterprise production |
Prerequisites
Cluster
Kubernetes 1.28+ cluster with at least 3 nodes. Managed clusters (EKS, GKE, AKS, Scaleway Kapsule) or self-managed.
Tools
kubectl 1.28+, Helm 3.12+, and optionally cert-manager 1.13+ for automatic TLS certificates.
Network
Ingress controller (nginx or traefik), DNS pointing to the ingress IP, outbound HTTPS for license validation.
Deployed resources
| Resource | Kind | Purpose |
|---|---|---|
| mislata-identity | Deployment | OAuth2/OIDC server, authentication, user management |
| mislata-api | Deployment | QuantumAPI EaaS — encryption, signatures, key management |
| mislata-worker | Deployment | Hangfire background jobs, QRNG entropy, license validation |
| mislata-postgresql | StatefulSet | Primary data store with persistent volume |
| mislata-redis | StatefulSet | Session cache, Data Protection keys, Hangfire job queue |
| mislata-ingress | Ingress | TLS termination, routing to identity and API services |
Ready to deploy on Kubernetes?
Follow our step-by-step Helm installation guide.
K8s Installation guide