Production

What you’ll accomplish

You’ll deploy UDS Core to a real Kubernetes cluster (cloud, on-premises, or airgapped). Unlike the local demo, you bring your own infrastructure and configure UDS Core for your environment.

This path is for the following audiences:

• Platform engineers standing up UDS Core for the first time
• Teams deploying to EKS, AKS, RKE2, K3s, or other on-prem environments
• Anyone migrating from an existing platform to UDS

What’s different from the local demo

Production deployments replace the local demo’s ephemeral defaults with your own infrastructure.

	Local Demo	Production
DNS	*.uds.dev (automatic)	Wildcard records pointing to your load balancers
TLS	TLS certs for uds.dev only	Real certificates for your domain
Log storage	In-cluster	Object storage (Loki: chunks, admin buckets)
Backup storage	In-cluster MinIO (dev only)	External object storage
Identity DB	Embedded dev-mode database (not for prod)	External database

Requirements

You need the following for a production deployment:

• A running CNCF-conformant Kubernetes cluster
• Wildcard DNS records for your admin and tenant domains
• TLS certificates
• Object storage for Loki and Velero (S3, GCS, Azure Blob, or S3-compatible)
• External database for Keycloak
• Sufficient cluster capacity (12+ vCPUs, 32+ GiB RAM across worker nodes)
• UDS CLI installed

Steps

Work through these steps to deploy UDS Core to production.

1. Prerequisites

   Validate your cluster, confirm node requirements, and verify networking and storage readiness.

2. Provision External Services

   Set up DNS, TLS certificates, object storage buckets, and the Keycloak PostgreSQL database.

3. Build Your Bundle

   Create a uds-bundle.yaml for your environment: choose a Core flavor, configure storage, TLS, and Keycloak overrides.

4. Deploy

   Deploy your bundle, monitor the rollout, and verify all components are healthy.

Note

Production deployments involve coordinating multiple systems: Kubernetes, DNS, certificates, storage, and databases. Expect to spend more time in prerequisites and provisioning than in the deployment itself.