Reverting an upgrade rolls SeekrFlow back to an earlier revision of its release. A rollback restores that revision’s chart and values, but changes the upgrade made to the databases stay. To undo those, restore the backup you took before you upgraded. See Upgrade a SeekrFlow deployment.
Roll back the release first, then restore the databases. If you restore first, the newer release is still running, and it upgrades the restored databases again.
Restoring the databases replaces them with the backup. Anything users created after the backup, such as accounts, agents, or files they uploaded, doesn’t survive the restore.
With the sfe CLI
Without the sfe CLI
Find the revision
The command lists each revision with its release version. Note the last revision that ran the version you’re returning to. Restore the databases
Check the backup and the plan first:Then restore:sfe asks you to type the namespace to confirm. To skip the prompt, such as in a script, add --yes. It stops every SeekrFlow service, replaces each database from the backup, and starts the services again. If the restore stops partway, the services stay stopped. That keeps anything from writing to a partly restored database. Run the same command again, or start the services on the databases as they are with sfe db restore --unquiesce -n seekrflow. Delete the migration jobs
A finished migration job left from the upgrade makes the next upgrade skip its migration. Find the revision
The command lists each revision with its chart version. Note the last revision that ran the version you’re returning to. Restore the databases
Stop SeekrFlow’s services, then restore each SeekrFlow database from the backup or snapshot you took before you upgraded, with your database’s restore tools. Start the services again after you restore every database.
Delete the migration jobs
A finished migration job left from the upgrade makes the next upgrade skip its migration. Check the deployment
Run the checks in Verify the deployment. 
