mirror of
https://github.com/cloudnative-pg/plugin-barman-cloud.git
synced 2026-09-05 06:32:21 +02:00
fb3397386c
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.Status.CurrentPrimary being unset, so it stops being added once that instance is up. CurrentPrimary is set by the instance manager itself, from inside the primary pod, only once it has completed its own bootstrap - unlike cluster.Status.Instances / IsInitialized(), which flips as soon as the instance's PVC exists, well before the pod is even created. Gating on IsInitialized() would mean the sidecar is never added to the one pod that needs it to perform its restore. Once CurrentPrimary is set, this makes the operator's own drift-check see the already-running pod's spec as outdated 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> |
||
|---|---|---|
| .. | ||
| config | ||
| rbac | ||
| specs | ||
| doc.go | ||
| identity.go | ||
| lifecycle_certificates.go | ||
| lifecycle_envs.go | ||
| lifecycle_resources.go | ||
| lifecycle_test.go | ||
| lifecycle.go | ||
| manager.go | ||
| reconciler.go | ||
| start.go | ||
| suite_test.go | ||