You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
TASK: Preserve PostgreSQL PVC labels across chart upgrades #217
Prevent Helm chart version changes from modifying immutable PostgreSQL StatefulSet volumeClaimTemplates fields during local SIT upgrades.
Root Cause
The merged infra-sit#31 chart bumped the PostgreSQL chart version from 0.1.0 to 0.2.0. The shared labels helper includes helm.sh/chart, and that label is rendered inside the immutable PVC template. Helm 4 server-side apply therefore rejected the upgrade before the database reconciliation Job ran.
Scope
Keep the existing PVC template label value stable while allowing chart metadata to evolve.
Preserve the existing StatefulSet, PVC, and data; do not use helm --force or delete storage.
Add a rendered-chart regression check for the stable PVC label.
The PostgreSQL rollout failure was traced to the chart-version label being rendered inside the immutable StatefulSet volumeClaimTemplates. The repair preserves the existing postgres-0.1.0 PVC-template label, adds a CI stability assertion, and documents the current database inventory.
PR #32 is ready for review. Merge order: infra-sit#31 is already merged; merge #32, then retry the PostgreSQL Helm upgrade. No deliberate delay is required beyond CI completion and branch visibility. No PVCs or data are deleted.
Activity
ramioooz commentedon Sep 4, 2026
Implementation PR: digital-bank-java/infra-sit#32
The PostgreSQL rollout failure was traced to the chart-version label being rendered inside the immutable StatefulSet volumeClaimTemplates. The repair preserves the existing
postgres-0.1.0PVC-template label, adds a CI stability assertion, and documents the current database inventory.PR #32 is ready for review. Merge order: infra-sit#31 is already merged; merge #32, then retry the PostgreSQL Helm upgrade. No deliberate delay is required beyond CI completion and branch visibility. No PVCs or data are deleted.