​

Deployment Operations

​

Deployment Model

• One folder per software (Dreambau-*)
• config/ holds Kubernetes manifests
• scripts/ provides deployment helpers
• Image builds are performed per service where needed

​

Standard Release Flow

1. Validate secrets and required environment values
2. Build and import image if service is locally built
3. Apply dependency resources (PVC, DB, cache, secrets)
4. Apply deployment and service manifests
5. Apply ingress and certificate resources
6. Wait for rollout completion and run smoke checks

​

Core Commands

kubectl apply -f <manifest>.yaml
kubectl rollout status deployment/<name> -n dreambau
kubectl logs -n dreambau deployment/<name> --tail=100

​

Post-Deploy Verification

• Pod and deployment are healthy
• Ingress route resolves correctly
• Certificate is valid
• Primary user flow works end-to-end

​

Change Control

• Use small incremental changes
• Verify service status after each change
• Avoid multi-service rollouts without rollback plan