Skip to main content
Qovery supports two deployment strategies for your applications.

​
RollingUpdate (Default)

The RollingUpdate strategy will gracefully rollout new versions of your application and automatically rollback if the new version fails to start. This is the recommended strategy as it avoids downtime and load spikes during deployments. Rolling Update Strategy

​
How it works

When using RollingUpdate:
  1. New pods are created with the new version
  2. Once the new pods are ready, traffic is gradually shifted to them
  3. Old pods are terminated only after new pods are healthy
  4. If new pods fail to start, the deployment automatically rolls back
This ensures your application remains available throughout the deployment process.

​
Recreate

The Recreate strategy will stop all current versions and create new ones once all old ones have been shutdown. Recreate Strategy

​
How it works

When using Recreate:
  1. All existing pods are terminated
  2. The system waits for all old pods to shut down completely
  3. New pods are created with the new version
  4. Service becomes available once new pods are ready
This strategy causes downtime but ensures only one version of your application runs at any time.

​
When to use Recreate

Use the Recreate strategy when:
  • Your application cannot run multiple versions simultaneously
  • You have breaking changes that are incompatible with the old version
  • You’re deploying to development or test environments where downtime is acceptable
  • Your application manages state that cannot be shared between versions

​
Next Steps

Deployment Pipeline

Configure deployment stages

Deployment Actions

Learn about deployment actions

Image Mirroring

Optimize deployments with image mirroring

Deployment Logs

Monitor your deployments