Recreate Deployment

Stop old version first, then start the new version.

deploy

Detailed Description

Recreate is acceptable for internal tools, non-critical systems, or planned maintenance periods.

For zero-downtime production paths, prefer blue-green, canary, or rolling updates instead.

This model is safest when background jobs are paused and clients can tolerate a maintenance window.

Because old and new versions never coexist, compatibility complexity is lower but availability risk is higher.

Use only when operational simplicity matters more than uninterrupted availability.

Stop v1
Downtime window
Start v2
Serve traffic again

Pros

Simple rollout with no mixed-version compatibility window

Cons

Causes downtime and higher release risk for user-facing systems

Examples: Kubernetes strategy: Recreate, controlled maintenance windows