Cloud
Rocket.Chat on Kubernetes (AKS GitOps + TLS + Cost Controls)
Rocket.Chat on AKS with Argo CD, Helm, TLS, external secrets, and scheduled scale-down windows.
Historical deployment. The hosted environment has been retired; source and recorded evidence remain available.
Kubernetes · Helm · AKS · ArgoCD · Traefik · cert-manager · MongoDB · NATS · External Secrets · Prometheus · Grafana
Overview
Sandbox Rocket.Chat deployment on Kubernetes designed for hands-on platform operations and SRE-style troubleshooting workflows.
Source
Deployment status
The hosted sandbox has been retired. This case study describes the earlier deployment.
What is included
- Helm deploy, upgrade, and rollback workflows
- Ingress routing and TLS via NGINX Ingress + cert-manager
- Resource sizing, health checks, and recovery drills
- Troubleshooting notes: logs, events, probes, config validation
Notes
Sandbox/lab environment. No production SLO or uptime claim.
Outcomes
Helm-based Rocket.Chat sandbox on Kubernetes with TLS ingress and documented troubleshooting steps.
Challenges and solutions
Challenges
- Providing a realistic Rocket.Chat deployment that is safe to run as a sandbox
- Hardening ingress exposure with TLS while keeping internal services private by default
- Documenting operational workflows for upgrades, failures, and common recovery tasks
- Keeping the setup reproducible and easy to iterate on during learning and testing
Solutions
- Standardized Helm deployment patterns with repeatable values and upgrade steps
- Used NGINX Ingress + cert-manager for TLS and controlled external exposure
- Kept internal services private (ClusterIP) and exposed only what is necessary
- Added operational guardrails: probes, resource requests/limits, and clear troubleshooting steps
Technology stack
Kubernetes
Kubernetes · Helm
Networking
NGINX Ingress · cert-manager · TLS
Data
MongoDB
Observability
Prometheus (optional) · Grafana (optional)
Application
Rocket.Chat