Skip to:
Hi,STR:
apply deploy/backup.yaml and with some incorrect option like:
wait several seconds and delete itkubectl delete -f deploy/backup.yaml -n postgres-operator
kubectl delete -f deploy/backup.yaml -n postgres-operator
change the backup name and fix the option and as a result the backup can’t start
In order to fix it you need to remove these annotations from PerconaPGCluster objectkubectl edit pg -n postgres-operator
kubectl edit pg -n postgres-operator
Now backups work correctly.
Verified.
the issue was fixed and will be available in 2.6.0.
I think we had similar issues before also :
I think the status of backup and Restore is not reconciled reliably.
Hi,
STR:
apply deploy/backup.yaml and with some incorrect option like:
wait several seconds and delete it
kubectl delete -f deploy/backup.yaml -n postgres-operatorchange the backup name and fix the option and as a result the backup can’t start
In order to fix it you need to remove these annotations from PerconaPGCluster object
kubectl edit pg -n postgres-operatorNow backups work correctly.