mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-21 20:23:39 +09:00
Tenants migrating spatial data need PostGIS, but the chart always runs the CloudNativePG PostgreSQL image, which does not ship it, and exposes no way to pick another one. CloudNativePG publishes a PostGIS operand image; a closed `flavor` enum selects it without handing tenants a free image field. The flavor pins the same PostgreSQL minor as the default one, on the standard-trixie variant: backups go through the barman-cloud plugin, so the deprecated system variant is not needed. update-versions.sh now derives the postgis map from the minors it picks, and a bats check fails if the two maps drift apart. The default images are built on bullseye and the postgis ones on trixie. Switching a live cluster between them would swap glibc under an initialised data directory and silently break every collatable index, and CNPG would roll it out as a plain image update. The chart therefore refuses a flavor change on an existing Cluster. Co-authored-by: Matthieu <matthieu@hidora.com> Assisted-by: LLM Signed-off-by: Mattia Eleuteri <mattia@hidora.io>
7 lines
220 B
YAML
7 lines
220 B
YAML
"v18": "18.1-3.6.1-standard-trixie"
|
|
"v17": "17.7-3.6.1-standard-trixie"
|
|
"v16": "16.11-3.6.1-standard-trixie"
|
|
"v15": "15.15-3.6.1-standard-trixie"
|
|
"v14": "14.20-3.6.1-standard-trixie"
|
|
"v13": "13.22-3.6.0-standard-trixie"
|