You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But it is not the case for the backup and restore jobs pods, even if it's possible to add custom labels for backup in the spec.backup.storages..labels section of the CR definition but nothing for restore as far as I know.
Anyway, it would be a great improvement to automatically add these labels for the backup and restore pods as it already the case with the PostgreSQL operator.
Steps to reproduce
1 - Create a pxc cluster with a backup storage configured without additional label in the definition
2 - Run a pxc backup of the cluster
3 - See that the backup job pod does not bear the classic app.kubernetes.io/* labels
4 - Run a pxc restore on the cluster
5 - See that the restore job pod does not bear the classic app.kubernetes.io/* labels neither
Versions
1 - Kubernetes - v1.27.6
2 - Operator - Percona Operator for MySQL based on Percona XtraDB Cluster 1.13.0
3 - Database - MySQL XtraDB 8.0
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Report
PXC backup and restore job pods do not bear the classic app.kubernetes.io/* labels used by other components
More about the problem
When a new pxc cluster is deployed, all the running pod related are automatically created with these usefull labels :
app.kubernetes.io/component=<pxc/haproxy/proxysql/pitr>
app.kubernetes.io/instance=<cr.Name>
app.kubernetes.io/managed-by=percona-xtradb-cluster-operator
app.kubernetes.io/name=percona-xtradb-cluster
app.kubernetes.io/part-of=percona-xtradb-cluster
But it is not the case for the backup and restore jobs pods, even if it's possible to add custom labels for backup in the spec.backup.storages..labels section of the CR definition but nothing for restore as far as I know.
Anyway, it would be a great improvement to automatically add these labels for the backup and restore pods as it already the case with the PostgreSQL operator.
Steps to reproduce
1 - Create a pxc cluster with a backup storage configured without additional label in the definition
2 - Run a pxc backup of the cluster
3 - See that the backup job pod does not bear the classic app.kubernetes.io/* labels
4 - Run a pxc restore on the cluster
5 - See that the restore job pod does not bear the classic app.kubernetes.io/* labels neither
Versions
1 - Kubernetes - v1.27.6
2 - Operator - Percona Operator for MySQL based on Percona XtraDB Cluster 1.13.0
3 - Database - MySQL XtraDB 8.0
Anything else?
No response
The text was updated successfully, but these errors were encountered: