The psmdb-operator chart exposes replicaCount, nodeSelector, affinity, and tolerations, but it does not render a PodDisruptionBudget.
Scheduled backups run in the operator leader process (robfig/cron), not as Kubernetes CronJobs. A missed tick is not backfilled. Voluntary disruption of the only replica at the scheduled time skips that backup.
A PDB does not help when replicaCount is 1 and maxUnavailable is 1 (eviction of the only pod is still allowed). The useful combination is replicaCount >= 2 with maxUnavailable: 1.
Please add an optional podDisruptionBudget block, default disabled so replicaCount: 1 stays unchanged, documented in the README.
Related: percona/percona-server-mongodb-operator#2526
The psmdb-operator chart exposes replicaCount, nodeSelector, affinity, and tolerations, but it does not render a PodDisruptionBudget.
Scheduled backups run in the operator leader process (robfig/cron), not as Kubernetes CronJobs. A missed tick is not backfilled. Voluntary disruption of the only replica at the scheduled time skips that backup.
A PDB does not help when replicaCount is 1 and maxUnavailable is 1 (eviction of the only pod is still allowed). The useful combination is replicaCount >= 2 with maxUnavailable: 1.
Please add an optional podDisruptionBudget block, default disabled so replicaCount: 1 stays unchanged, documented in the README.
Related: percona/percona-server-mongodb-operator#2526