Updating the Percona Operator to 1.9.0 or 1.10.0 does not delete existing backup cronjobs
General
Escalation
General
Escalation
Description
In Percona Kubernetes Operator for Percona XtraDB Cluster 1.6.0, cronjobs are used for scheduling backups:
However, after updating the operator to Percona Distribution for MySQL Operator 1.9.0 or 1.10.0, these cronjobs still exist:
Updating to 1.10.0:
Cron jobs still exist after upgrade:
As per https://jira.percona.com/browse/K8SPXC-701, scheduling does not use cronjobs anymore. However, since these jobs are not deleted, backups will be performed twice.
The workaround is to delete the cronjobs manually:
In Percona Kubernetes Operator for Percona XtraDB Cluster 1.6.0, cronjobs are used for scheduling backups:
However, after updating the operator to Percona Distribution for MySQL Operator 1.9.0 or 1.10.0, these cronjobs still exist:
Updating to 1.10.0:
Cron jobs still exist after upgrade:
As per https://jira.percona.com/browse/K8SPXC-701, scheduling does not use cronjobs anymore. However, since these jobs are not deleted, backups will be performed twice.
The workaround is to delete the cronjobs manually: