The GitHub Actions job "Release Auditing" on texera.git/fix/helm-release-name has failed. Run started by GitHub user aicam (triggered by aicam).
Head commit for run: d3b574542a60037df734e875af5bb8b4ded902e1 / ali <[email protected]> fix(k8s): make the Helm chart work under any release name The chart derives in-cluster hostnames from `.Release.Name`, but the lakefs and lakekeeper sub-charts address Postgres and MinIO from their own values blocks, where the names are hardcoded as `texera-postgresql` and `texera-minio`. Helm does not template values files, so those references cannot be release-derived and silently point at Services that do not exist unless the release happens to be named `texera`: $ helm install myrel bin/k8s Secret/myrel-lakefs database_connection_string -> texera-postgresql ConfigMap/myrel-lakefs blockstore.endpoint -> texera-minio:9000 Secret/myrel-lakekeeper-config-envs LAKEKEEPER__PG_HOST_{R,W} -> texera-postgresql while the Services actually created are `myrel-postgresql` / `myrel-minio`. LakeFS and Lakekeeper then fail to reach the database and the object store. Pin the two sub-charts with `fullnameOverride` so the names the sibling values reference are constants, and resolve them in chart templates through new `texera.postgresql.fullname` / `texera.minio.fullname` helpers so both sides always agree. The helpers fall back to the previous `<release>-<chart>` form if the override is cleared. Give the generated S3 credentials Secret a fixed name for the same reason -- `values-aws.yaml` wires it into `lakefs.extraEnvVars` and carried a note telling the user to hand-edit it; that note is no longer needed. Rendering release `texera` is byte-identical to before (all three values files), so existing deployments are unaffected. Signed-off-by: ali <[email protected]> Report URL: https://github.com/apache/texera/actions/runs/32292842316 With regards, GitHub Actions via GitBox
