Service Management

Deploy versioned services with health checks and a reversible rollout.

Each change creates a revision#

A revision combines the image digest, runtime configuration, secret references, and resource requests for a service. Revisions are immutable; changing a setting creates a new revision with a separate rollout history.

du services revisions catalog
du services rollout catalog --revision rev-024 --wait
du services rollback catalog --revision rev-023

Control a rollout#

rollout:
  strategy: rolling
  maxUnavailable: 0
  maxSurge: 1
readiness:
  path: /health/ready
  initialDelaySeconds: 5
  failureThreshold: 3

New replicas receive traffic only after readiness succeeds. A rollout pauses when the readiness budget is exceeded, leaving healthy previous replicas in service.

Plan for data compatibility#

A runtime rollback does not reverse a database migration. Use backward-compatible schema changes so both the old and new application revisions can run during a rollout.