Upgrade Clouisle
Safely update images, migrate data, and roll back on failure
Before upgrading, read the target version's CHANGELOG and confirm database migrations, Workflow definitions, model adapters, and deployment manifest changes.
Compose Upgrade
- Back up PostgreSQL, Qdrant, upload volumes, and
.env. - Pull the new images:
docker compose pull. - Review each service's configuration and image tags.
- Run
docker compose up -dand watch theapiand Worker logs first. - Check
/api/v1/health, login, model list, Knowledge Base retrieval, and one published Agent. - Check whether old Workflow definitions need to be re-saved with
schema_version: 2.
The installer upgrade preserves the existing .env, but you still need to review new variables and defaults.
Kubernetes Upgrade
Run helm upgrade with the same release and namespace, or review and apply newly generated manifests. Update the API and migrations first, then Worker/Beat/Frontend; keep Beat at a single replica during production.
Rollback
Before rolling back images, confirm whether the database migration is reversible. If the migration is not reversible, do not just switch back to the old image; restore a backup in an isolated environment and verify. Workflow versions can be restored separately in the product UI, but this is not equivalent to a service rollback.
How is this guide?