Skip to:
User impact:
Steps to reproduce:
Setup Everest (FE, BE and Kubernetes cluster)
Create a storage location
Create a PG DB Cluster (1 or 3 node)
Create Backup
Check CR for the DB cluster
Additional:
Delete the backup
Actual result:
Missing storage location information
Backup pod not deleted
Expected result:
CR contains all the required information for a successful backup and restore
Delete all relative pods if backup deleted
Yes, we can close this ticket. Thanks
From my understanding all that's needed to be done regarding this ticket is the subtask . Hence, I promoted it to separate task.
Please confirm this is the case. If this is true I think we can close this one.
Added the subtask for UI to generate unique names for backups which is gonna fix the immediate recreation of the backups after deletion.
Discussed the fix version with and we agreed it's important to be able to create more than one backup in 0.3.0, so the fix version is updated.
The ticket for 3: https://jira.percona.com/browse/K8SPG-432
For 1. You are right, I was using the wrong command to check for PG backup CR. Video attached.For 2. I think we can do that, Slava has put this ticket in 0.4.0, let's wait it, and we can solve it at then if it's okay as this is not a blocker.
User impact:
Steps to reproduce:
Setup Everest (FE, BE and Kubernetes cluster)
Create a storage location
Create a PG DB Cluster (1 or 3 node)
Create Backup
Check CR for the DB cluster
Additional:
Delete the backup
Actual result:
Missing storage location information
Backup pod not deleted
Expected result:
CR contains all the required information for a successful backup and restore
Delete all relative pods if backup deleted