Skip to main content
Upgrading moves SeekrFlow to a newer release. Some releases change defaults, or need steps before or after the upgrade. Each release’s notes list these under its upgrade considerations. Before you start, read the release notes for every version between yours and the new one.

Before you upgrade

1

Back up the databases

An upgrade can change the database schema, and rolling back the release doesn’t undo that. Restoring this backup does:
The backup holds password hashes and other secrets. Store it as securely as the database itself. It doesn’t include files in object storage. On a managed database service, also take a snapshot.
2

Replace the image pull secret if your registry token changed

Registry tokens expire once a year. If yours changed, delete the image pull secret and create it again in both the seekrflow and argo-workflows namespaces. If you mirrored the images, use your own registry and its credentials instead of Seekr’s:

Upgrade

1

Run preflight

sfe upgrade doesn’t run preflight for you.
2

Upgrade

sfe downloads the new release’s chart and upgrades in place.
To apply a changed values file without changing versions, run sfe upgrade -p <profile-name> without -r.

Check the upgrade

Run the checks in Verify the deployment. SeekrFlow reloads its model catalog during the upgrade.
Last modified on October 16, 2026