Repository navigation
Commit 892bad8
fix(keycloak): use barman-capable system image when backups enabled
The Keycloak DB backup (#3174) uses the in-tree native `barmanObjectStore`,
whose `barman-cloud-*` binaries ship ONLY in the CNPG `system` image variant.
Since #2342 the DB is pinned to the `standard` variant, which omits them — so
with backups enabled a base backup fails `barman-cloud-backup: executable file
not found` and WAL archiving cannot run (also risks WAL accumulation).
Pin the barman-capable `system` variant only when backups are enabled
(backup.enabled + destinationPath); otherwise keep `standard`. Verified on a
freedom-portal cluster: with `system-trixie` the CNPG Backup completes and WAL
archiving works to S3; with `standard-trixie` it fails as above.
TEMPORARY bridge: `system` is deprecated in CNPG 1.27 (removed in 1.29). Remove
this once Postgres backups migrate to the Barman Cloud Plugin — see #3300.
Refs #3300, #2342, #3174.
Co-Authored-By: Claude Opus 4.8 <[email protected]>1 parent 77389d6 commit 892bad8
1 file changed
Lines changed: 13 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
6 | 6 | | |
7 | 7 | | |
8 | 8 | | |
9 | | - | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
10 | 22 | | |
11 | 23 | | |
12 | 24 | | |
| |||
0 commit comments