Add HA for CV and Docs: zero-downtime deploys #273

Merged

eblume merged 1 commit from feature/ha-cv-docs-zero-downtime into main

2026-02-26 07:53:22 -08:00

eblume commented

2026-02-26 07:44:26 -08:00

Owner

Summary

Set replicas: 2 with maxUnavailable: 0 / maxSurge: 1 on CV and Docs deployments so rolling updates never drop below 2 ready pods
Add PodDisruptionBudgets (minAvailable: 1) to protect against node drains and cluster maintenance
Add Fly.io cache purge step to cv-deploy.yaml workflow (docs already had this) so CV deploys don't serve stale cached content

Deployment and Testing

argocd app diff cv / argocd app diff docs from branch
Deploy from branch: argocd app set cv --revision feature/ha-cv-docs-zero-downtime && argocd app sync cv
Verify 2 pods running: kubectl get pods -n cv --context=minikube-indri
Test rolling restart: kubectl rollout restart deployment/cv -n cv --context=minikube-indri
During rollout, confirm continuous availability via curl -I https://cv.eblu.me
After merge: reset ArgoCD to main, re-sync both apps

## Summary - Set `replicas: 2` with `maxUnavailable: 0` / `maxSurge: 1` on CV and Docs deployments so rolling updates never drop below 2 ready pods - Add PodDisruptionBudgets (`minAvailable: 1`) to protect against node drains and cluster maintenance - Add Fly.io cache purge step to `cv-deploy.yaml` workflow (docs already had this) so CV deploys don't serve stale cached content ## Deployment and Testing - [ ] `argocd app diff cv` / `argocd app diff docs` from branch - [ ] Deploy from branch: `argocd app set cv --revision feature/ha-cv-docs-zero-downtime && argocd app sync cv` - [ ] Verify 2 pods running: `kubectl get pods -n cv --context=minikube-indri` - [ ] Test rolling restart: `kubectl rollout restart deployment/cv -n cv --context=minikube-indri` - [ ] During rollout, confirm continuous availability via `curl -I https://cv.eblu.me` - [ ] After merge: reset ArgoCD to main, re-sync both apps

eblume added 1 commit

2026-02-26 07:44:26 -08:00

Add HA for CV and Docs: 2 replicas, rolling updates, PDBs 74dcddd9fb

- Set replicas: 2 with maxUnavailable: 0 / maxSurge: 1 on both
  deployments so rolling updates never drop below 2 ready pods
- Add PodDisruptionBudgets (minAvailable: 1) to protect against
  node drains and cluster maintenance
- Add Fly.io cache purge step to cv-deploy workflow (docs already
  had this) so CV deploys don't serve stale cached content

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>