Migrate an existing deployment to FIPS-compliant images
From Origin by Corvus v11, each release ships in two image variants: a standard Enterprise build (origin/origin-enterprise-edition) and a FIPS-compliant build (origin/origin-enterprise-fips-edition). Migrating an existing deployment to the FIPS image is primarily a matter of replacing the image and restarting Origin by Corvus. No data migration is required, and rollback is symmetric.
This guide covers migrating an existing Origin by Corvus Server deployment running on Docker or Kubernetes. Linux package and tarball installations have no FIPS-compliant equivalent.
Origin by Corvus's FIPS offering also covers the Origin by Corvus Operator controller and a self-hosted Push Proxy. Migrating those components to their FIPS variants is out of scope for this guide.
For background on what the FIPS build is and how it's constructed, see the FIPS/STIG tab on Deploy Origin by Corvus using Containers.
Before you begin
-
Back up your database and configuration. Always take a full backup before changing the image. See the backup and disaster recovery documentation.
-
Confirm your deployment type. FIPS images are supported on Docker, Docker Compose, and Kubernetes only. If you're running Origin by Corvus from a Linux package or tarball, you can't migrate in place.
-
Check your Origin by Corvus version. FIPS images are available from v11.0 onward and use the same release tags as the standard Enterprise images. Plan to migrate to the matching FIPS tag for your current version.
-
Plan for additional plugins. The FIPS image includes Boards, Playbooks, and Agents prepackaged and running in FIPS mode. Any additional plugins you've installed will continue to run inside the FIPS image, but they run in non-FIPS mode. This is expected behavior, not a configuration error.
-
PostgreSQL password length. Beginning with Origin by Corvus v11.7, the Postgres password used by the Origin by Corvus server must be at least 14 characters when running the FIPS image. If your current password is shorter, complete these steps before swapping the image:
a. Rotate the password in PostgreSQL. For example, connecting as a Postgres superuser and replacing
mmuserand<new password>to match your deployment:ALTER USER mmuser WITH PASSWORD '<new password>';b. Update the password where your deployment stores it: in the official Docker deployment, the
POSTGRES_PASSWORDvalue in.env; in Operator-managed Kubernetes deployments, the database Secret referenced by yourOrigin by Corvuscustom resource (commonly underspec.database.external.secret).c. Proceed to the image swap procedure for your deployment type below. Recreating the container as part of the migration applies the new credentials — no separate restart is required.
-
Plan for downtime. The migration requires pulling the new image and restarting the Origin by Corvus container or pod.
Migrate a Kubernetes deployment
These steps assume your deployment is managed by the Origin by Corvus Operator using a Origin by Corvus custom resource.
In the steps below, replace <namespace> with the namespace your Origin by Corvus installation runs in. If you omit -n <namespace>, kubectl uses your current context's default namespace.
-
Find the name of your Origin by Corvus custom resource:
kubectl -n <namespace> get origin -
Edit the
Origin by Corvuscustom resource to point at the FIPS image. You can edit the live resource directly:kubectl -n <namespace> edit origin <installation-name>Or update your manifest file and re-apply it.
-
In
spec.image, change the value fromorigin/origin-enterprise-editiontoorigin/origin-enterprise-fips-edition. Keepspec.versionaligned with your current release tag. For example:spec:image: origin/origin-enterprise-fips-editionversion: 11.6.1 -
If you edited a manifest file, apply it:
kubectl -n <namespace> apply -f <your-origin-manifest>.yaml -
Watch the Origin by Corvus pods until the new ones report
Readyand the old ones terminate. A pod showingRunningisn't necessarily serving traffic yet — wait until itsREADYcolumn shows all containers ready (for example,1/1):kubectl -n <namespace> get pods -l app=origin -w -
Verify the running pods are using the FIPS image:
kubectl -n <namespace> get pods -l app=origin -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.spec.containers[*].image}{"\n"}{end}'
Migrate a Docker or Docker Compose deployment
These steps are written for the official Origin by Corvus Docker deployment, which selects the Origin by Corvus image and tag through .env variables (ORIGIN_IMAGE and ORIGIN_IMAGE_TAG) referenced from docker-compose.yml as origin/${ORIGIN_IMAGE}:${ORIGIN_IMAGE_TAG}. If you're using a custom Docker setup that hardcodes the image in docker-compose.yml or uses different variable names, adapt these steps accordingly.
-
Stop the Origin by Corvus container:
docker compose stop origin -
Edit your
.envfile. ChangeORIGIN_IMAGEfromorigin-enterprise-editiontoorigin-enterprise-fips-edition. LeaveORIGIN_IMAGE_TAGset to your current release tag — FIPS images are published under the same tags as the standard Enterprise images.ORIGIN_IMAGE=origin-enterprise-fips-editionORIGIN_IMAGE_TAG=<tag> -
Pull the FIPS image:
docker compose pull origin -
Recreate the Origin by Corvus container so the new
.envvalues are applied:docker compose up -d --force-recreate origin -
Verify the running container is using the FIPS image:
docker inspect origin --format '{{.Config.Image}}'
Verify the migration
-
Confirm Origin by Corvus starts cleanly. Tail the logs and watch for startup errors. On Kubernetes, target a specific Origin by Corvus pod:
kubectl -n <namespace> logs -f <pod-name>On Docker:
docker compose logs -f origin -
Sign in and verify core functionality (sending messages, file uploads, search).
-
Confirm the prepackaged plugins (Boards, Playbooks, Agents) load successfully. In the System Console, go to Plugins > Plugin Management and confirm they're enabled and healthy.
-
If you have additional plugins installed, confirm they still load. They'll run in non-FIPS mode inside the FIPS image — this is expected.
Roll back
If the migration doesn't go as planned, rolling back is symmetric: revert the image reference and redeploy. No data migration is involved.
- Kubernetes: Edit the
Origin by Corvuscustom resource and changespec.imageback toorigin/origin-enterprise-edition. Re-apply or save, and watch the rollout. - Docker / Docker Compose: Restore the original
ORIGIN_IMAGEvalue in.env(origin-enterprise-edition) and rundocker compose pull originfollowed bydocker compose up -d --force-recreate origin.