Backup and pods are not deleted if the db cluster is deleted
Description
Tested on gke using v0.2.0 docker image in quickstart.yml Create a mysql db cluster. Then take its backup. After the backup is successful, delete the db cluster. In the below, all the mysql database pods are deleted, but backup pod is not deleted.
This issue wasn’t observed after the mysql, mongodb databases were deleted.
The issue of the postgresql initial backup not being deleted will be fixed in .
Hence closing this issue.
Manish Chawla
April 8, 2024 at 2:20 PM
Hi , This works for mysql and mongodb, but for postgresql, one backup remains after the database deletion
Please check, thanks.
Manish Chawla
September 21, 2023 at 11:58 AM
If we create a new database with the same name as the one deleted, then it shows the old backups for the new database, which is incorrect as this is a new database for which no backups should exist, for example
To reproduce this 1. Create a mysql database with name mysql-abcd 2. Add some data and take two backups named backup-mysql-abcd and backup-mysql-abcd-2 3. Delete the mysql database 4. Create the mysql database again with the same name mysql-abcd 5. The same backups backup-mysql-abcd and backup-mysql-abcd-2 are displayed for the new database mysql-abcd 6. Use the backup-mysql-abcd to restore the backup to the same database, the mysql-abcd database comes up but the backup data isn't restored
Tested on gke using v0.2.0 docker image in quickstart.yml
Create a mysql db cluster. Then take its backup. After the backup is successful, delete the db cluster. In the below, all the mysql database pods are deleted, but backup pod is not deleted.