From 56499b91f412167ac0460590bd4952b15c4cf872 Mon Sep 17 00:00:00 2001 From: Jeremy Date: Thu, 14 May 2026 20:35:39 +0200 Subject: [PATCH] fix(helm): remove stale Chart.lock that pulls in conflicting Bitnami postgresql sub-chart Chart.yaml has no dependencies section, but Chart.lock still references bitnami/postgresql@15.5.38. Helm and GitOps controllers (e.g. Flux helm-controller) run `helm dependency build` whenever Chart.lock is present, which downloads and packages the Bitnami sub-chart. This causes two StatefulSets named hindsight-postgresql to be rendered: one from the chart's own postgresql-statefulset.yaml template and one from charts/postgresql/templates/primary/statefulset.yaml (Bitnami). They have conflicting spec.selector.matchLabels, so the second apply is rejected by Kubernetes with an immutable field error. The Bitnami security context (readOnlyRootFilesystem: true, runAsUser: 1001) also crashes the ankane/pgvector container which needs to write to /var/run/postgresql. Since Chart.yaml lists no dependencies, Chart.lock is stale and serves no purpose. Removing it prevents the Bitnami sub-chart from being downloaded. --- helm/hindsight/Chart.lock | 6 ------ 1 file changed, 6 deletions(-) delete mode 100644 helm/hindsight/Chart.lock diff --git a/helm/hindsight/Chart.lock b/helm/hindsight/Chart.lock deleted file mode 100644 index 68f777770..000000000 --- a/helm/hindsight/Chart.lock +++ /dev/null @@ -1,6 +0,0 @@ -dependencies: -- name: postgresql - repository: https://charts.bitnami.com/bitnami - version: 15.5.38 -digest: sha256:f67c7612736803ece8a669f8ca6b0555f3b78557bc0ecb732aa2e43f0df7750d -generated: "2025-12-10T17:20:57.058794+01:00"