Cloud Providers
AWS
EKS (Elastic Kubernetes Service)
The Kubernetes manifests in services/orchestrator/k8s/ work directly on EKS:
1# Configure kubectl for EKS2aws eks update-kubeconfig --name your-cluster --region us-east-134# Create namespace and secrets5kubectl create namespace orcher6kubectl create secret generic orcher-secrets \7 --namespace=orcher \8 --from-literal=database-url='postgresql://orcher:PASSWORD@your-rds.us-east-1.rds.amazonaws.com:5432/orcher?sslmode=require' \9 --from-literal=redis-url='redis://your-elasticache.us-east-1.cache.amazonaws.com:6379'1011# Deploy12cd services/orchestrator/k8s13kubectl apply -k .For secrets, consider AWS Secrets Manager with the External Secrets Operator instead of plain Kubernetes secrets.
ECS (Elastic Container Service)
Run the orchestrator as an ECS service with Fargate:
- Push the image to ECR
- Create a task definition with the container image, environment variables, port mappings (50051, 8080), and health check (
/health/live) - Create an ECS service with the task definition behind a Network Load Balancer (NLB) for gRPC
- Configure security groups to allow inbound on ports 50051 and 8080
Key considerations for ECS:
- Use NLB (not ALB) for gRPC traffic — ALB supports gRPC but NLB has lower latency
- Set
DATABASE_URLandREDIS_URLvia ECS task definition secrets referencing Secrets Manager - Enable ECS Service Connect or Cloud Map for service discovery
GCP
GKE (Google Kubernetes Engine)
1# Configure kubectl for GKE2gcloud container clusters get-credentials your-cluster --zone us-central1-a34# Create namespace and secrets5kubectl create namespace orcher6kubectl create secret generic orcher-secrets \7 --namespace=orcher \8 --from-literal=database-url='postgresql://orcher:PASSWORD@/orcher?host=/cloudsql/project:region:instance' \9 --from-literal=redis-url='redis://10.0.0.3:6379'1011# Deploy12cd services/orchestrator/k8s13kubectl apply -k .For Cloud SQL, use the Cloud SQL Auth Proxy as a sidecar container for secure, IAM-authenticated connections without managing SSL certificates.
Cloud Run
Cloud Run can host the orchestrator for lower-traffic deployments:
- Push the image to Artifact Registry
- Deploy with gRPC port mapping and Cloud SQL connection
- Set minimum instances to 1 (the orchestrator needs persistent connections)
Cloud Run limitations to consider:
- Request timeout — Maximum 60 minutes per request (sufficient for gRPC long-polling)
- Cold starts — Set minimum instances > 0 to avoid startup latency
- VPC connector — Required for Cloud SQL and Memorystore private IP access
Azure
AKS (Azure Kubernetes Service)
1# Configure kubectl for AKS2az aks get-credentials --resource-group your-rg --name your-cluster34# Create namespace and secrets5kubectl create namespace orcher6kubectl create secret generic orcher-secrets \7 --namespace=orcher \8 --from-literal=database-url='postgresql://orcher:PASSWORD@your-server.postgres.database.azure.com:5432/orcher?sslmode=require' \9 --from-literal=redis-url='redis://your-cache.redis.cache.windows.net:6380,password=KEY,ssl=True'1011# Deploy12cd services/orchestrator/k8s13kubectl apply -k .Azure Database for PostgreSQL Flexible Server includes built-in PgBouncer — enable it in the server parameters to avoid deploying a separate connection pooler.
Next Steps
- Managed Databases — PostgreSQL, PgBouncer, and Redis configuration
- Operations — High availability, monitoring, and secrets management
- Cloud Platforms Overview — Architecture and container image setup