ge or if the ZenML version doesn't change at all).a backup file or database is created before every database migration attempt (i.e. during every Helm upgrade). If a backup already exists (i.e. persisted in a persistent volume or backup database), it is overwritten.

the persistent backup file or database is cleaned up after the migration is completed successfully or if the database doesn't need to undergo a migration. This includes backups created by previous failed migration attempts.

the persistent backup file or database is NOT cleaned up after a failed migration. This allows the user to manually inspect and/or apply the backup if the automatic recovery fails.

The following example shows how to configure the ZenML server to use a persistent volume to store the database dump file:

zenml:

# ...

database:

url: "mysql://admin:password@my.database.org:3306/zenml"

# Configure the database backup strategy

backupStrategy: dump-file

backupPVStorageSize: 1Gi

podSecurityContext:

fsGroup: 1000 # if you're using a PVC for backup, this should necessarily be set.

PreviousDeploy with Docker

NextDeploy using HuggingFace Spaces

Last updated 15 days ago