Backup tests in your cluster.
The RestoreTrust worker restores backups and runs checks in your Kubernetes cluster. You choose the location and control access to your backups.
Add the worker to your project
Install the worker in your Kubernetes cluster and assign it to a project. In the test schedule, select the worker that should run the tests. It must belong to the same project and is used for both scheduled and manually started tests.
The worker needs access to your backup source. Allow enough computing power, memory, and storage for the backup and the restored database.
A separate environment for each test
For a database test, the worker downloads the backup and restores it into a dedicated test database. The restore runs separately from your production database. Your checks then run against the restored data. The temporary environment is removed after the test.
File checks do not need a database: they check the backup file against the requirements you have set.
Credentials stay in your cluster
Store the credentials for your backup sources as Kubernetes Secrets in your cluster. In RestoreTrust, enter the name of each Secret. The test environment uses the credentials locally; the central application does not access your backup storage directly.
Store any archive passwords and decryption keys in the cluster too. This is where you manage, change, and delete your Secrets.
Limit network access
The installation sets up network rules for the test environment. You decide which connections are allowed for name resolution and backup access. Your cluster’s network plugin must support Kubernetes NetworkPolicies for these rules to take effect.
An optional admission policy can protect the rules against unauthorised changes that would widen access. This requires Kubernetes 1.30 or later.
Follow the results in the Console
Restores and file checks run in your cluster. Status updates, logs, and check results are sent to RestoreTrust. In the Console, you can see how a test went and which step failed if an error occurred.
Depending on your plan, you can also include the results in reports for your team or an audit. See Security for more about access permissions and test evidence.