Upgrade
Upgrading GES means pulling new images and restarting the services. Database migrations run automatically.
Before upgrading
Make a backup. You will need it to return to the state before the upgrade if something goes wrong. See Backup.
Check what changed in the new version in Release Notes.
Install with Docker Compose
In docker-compose.yaml, GES images use the latest tag, so pulling downloads the latest version.
To upgrade GES with one command, run in the folder with docker-compose.yaml:
docker compose up -d --pull=always
If AI features are on, add the ai profile:
docker compose --profile ai up -d --pull=always
To verify the signature of the new images before restarting, upgrade step by step:
Pull the images:
docker compose --profile ai pullWithout AI features, run the command without
--profile ai.List the images and verify the signature of each GES image. See Image Signature Verification.
docker compose --profile ai config --imagesRestart the services:
docker compose --profile ai up -d
Install with Helm
Update the chart list:
helm repo updateUpgrade the release with the same chart and
values.yamlas at installation:helm upgrade gramax gramax/gramax-enterprise-server-in-k8s -n <...> -f values.yamlIf you used an existing Secret at installation, pass the same parameters:
helm upgrade gramax gramax/gramax-enterprise-server-in-k8s \ -n <...> \ -f values.yaml \ --set secrets.create=false \ --set secrets.name=gramax-app-secrets
Verify the signature of the new images as at installation — see Image Signature Verification.
Database migrations
You don't need to run migrations separately. At start, the enterprise service connects to the database and runs the migrations itself. See GES Database.
After upgrading
Check that the services work: request /health/readiness and the detailed /health. If a database is connected to GES, the postgresql module in the /health response must have the healthy status. See Service health checks.