Skip to content

Upgrade the node

  1. Read release notes for Docker images, Kong, PostgreSQL, HAPI FHIR, and the application revision.
  2. Confirm FHIR-version and database compatibility.
  3. Complete and test a backup.
  4. Capture current image digests and pin target images; do not deploy an unreviewed latest tag.
  5. Rehearse the upgrade and rollback using restored production-like data.

Schedule a maintenance window, stop incoming traffic, pull the approved images, and start the stack. Kong schema migration runs through kong-migration; review its logs before allowing Kong traffic. Do not downgrade a migrated database unless the release procedure explicitly supports it.

Terminal window
docker compose pull
docker compose up -d
docker compose logs --tail=200 kong-migration

Run the complete verification checklist before reopening access.

If application rollback is compatible with the migrated schema, restore the recorded image digests and configuration. Otherwise restore both databases and application state from the pre-upgrade backup. Record the failure and retain sanitized logs.