Docker and Kubernetes deployment
DevOps and platform engineers self-hosting the tnc-sh control plane.
Self-host tnc-sh with Docker Compose for local or single-node trials, or Kubernetes for clustered production — including image build notes and a hardening checklist.
These paths target operators running the control plane themselves. Managed tnc-sh.cloud projects do not require this guide unless you are mirroring the stack on-premises.
5 sections4 key takeaways3 related guides
Quick highlights
These paths target operators running the control plane themselves. Managed tnc-sh.cloud projects do not require this guide unless you are mirroring the stack on-premises.
Use Compose for local integration testing; use Kubernetes with the hardening checklist for production-shaped self-hosted deployments.
What you will learn
- Docker Compose bundles API, web, worker, beat, Postgres, and Redis for quick bring-up.
- Kubernetes manifests under
k8s/expect ingress, cert-manager, and a default StorageClass. - Bake
NEXT_PUBLIC_API_URLat web image build time — runtime env alone is insufficient for the client bundle. - Replace placeholder secrets and
latesttags before any production-facing rollout.
Sections in this guide