Skip to:
Five days ago we deleted a cluster with kubectl delete pg pgha-cluster1 -n percona-operator.
We are still seeing the following log messages every few seconds in the logs for the percona operator:
│ 2025-03-17T18:58:09.121Z ERROR WALWatcher get latest backup {"controller": "perconapgcluster", "controllerGroup": "pgv2.percona.com", "controllerKind": "PerconaPGCluster", "PerconaPGCluster": {"name":"pgha-cluster1","namespace":"percona-operator"}, "namespace": "postgres-operator", "name": "pgha-cluster1", "reconcileID": "184bffed-9908-465b-8784-394b8535f0b8", "error": ││ runtime.goexit ││ /usr/local/go/src/runtime/asm_amd64.s:1695
What is causing the operator to continue to look for backups after the cluster was deleted?
Percona operator 2.5.0 and Kubernetes 1.30
Five days ago we deleted a cluster with kubectl delete pg pgha-cluster1 -n percona-operator.
We are still seeing the following log messages every few seconds in the logs for the percona operator:
│ 2025-03-17T18:58:09.121Z ERROR WALWatcher get latest backup {"controller": "perconapgcluster", "controllerGroup": "pgv2.percona.com", "controllerKind": "PerconaPGCluster", "PerconaPGCluster": {"name":"pgha-cluster1","namespace":"percona-operator"}, "namespace": "postgres-operator", "name": "pgha-cluster1", "reconcileID": "184bffed-9908-465b-8784-394b8535f0b8", "error": │
│ runtime.goexit ││ /usr/local/go/src/runtime/asm_amd64.s:1695
What is causing the operator to continue to look for backups after the cluster was deleted?