plugin-barman-cloud/internal/cnpgi
Marco Nenciarini e95b91dee9
fix: stop keeping the sidecar forever on recovery-only clusters
A cluster bootstrapped only via RecoveryBarmanObjectName, with no
continuing archiving or replica source, only ever needs the sidecar
for its one-time bootstrap restore. Gate its injection on
cluster.IsInitialized() so it stops being added once the cluster is
up.

This makes the operator's own drift-check see the already-running
pod's spec as outdated right after initialization completes, and roll
it out to drop the sidecar. That is deliberately accepted rather than
engineered around: it is one deterministic rollout using the same
machinery the operator already uses for every other pod-spec change
(a switchover if a replica is available, an in-place restart
otherwise), not a new or fragile risk.

Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
2026-07-27 20:25:38 +02:00
..
common feat: serve restore hooks from the instance sidecar 2026-07-27 16:36:09 +02:00
instance feat: serve restore hooks from the instance sidecar 2026-07-27 16:36:09 +02:00
metadata chore(main): release 0.13.0 (#860) 2026-06-10 10:55:17 +02:00
operator fix: stop keeping the sidecar forever on recovery-only clusters 2026-07-27 20:25:38 +02:00
restore feat: serve restore hooks from the instance sidecar 2026-07-27 16:36:09 +02:00