Installer script ignores custom overrides due to incorrect CONFIG_DIR path in install-postgres-operator.sh #1230
Description
Describe the bug
I created a custom Helm override file to redirect images to an internal registry and adjust configurations for the Postgres Operator: /etc/genestack/helm-configs/postgres-operator/postgres-operator-helm-overrides.yaml
To Reproduce
Steps to reproduce the behavior:
- Updated the required override config for Postgres Operator in
/etc/genestack/helm-configs/postgres-operator/postgres-operator-helm-overrides.yaml. - Run the postgres-operator deployment Script
/opt/genestack/bin/install-postgres-operator.sh - Check that the postgres-operator pod is running or not.
Expected behavior
The custom helm overrides should be applied while running the postgres-operator deployment Script.
Screenshots
(genestack) root@controller01:~# /opt/genestack/bin/install-postgres-operator.sh
/opt/genestack/submodules/postgres-operator/charts ~
Executing Helm command:
helm upgrade --install postgres-operator ./postgres-operator --version 1.12.2 --namespace=postgres-system --create-namespace --timeout 120m -f /opt/genestack/base-helm-configs/postgres-operator/postgres-operator-helm-overrides.yaml
Release "postgres-operator" does not exist. Installing it now.
NAME: postgres-operator
LAST DEPLOYED: Wed Oct 8 02:59:00 2025
NAMESPACE: postgres-system
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
To verify that postgres-operator has started, run:
kubectl --namespace=postgres-system get pods -l "app.kubernetes.io/name=postgres-operator"
~Server (please complete the following information):
- OS: 22.04
Additional context
The installer script /opt/genestack/bin/install-postgres-operator.sh is hardcoding the CONFIG_DIR variable incorrectly:
CONFIG_DIR="/etc/genestack/helm-configs/postgres-operator/base"As a result, it never loads the user-defined overrides from:
/etc/genestack/helm-configs/postgres-operator/postgres-operator-helm-overrides.yamlThis causes the Helm install command to always use the base configuration from:
/opt/genestack/base-helm-configs/postgres-operator/and ignore any local customizations.
To fix this issue I updated the installer script CONFIG_DIR=/etc/genestack/helm-configs/postgres-operator
Rerun the installer script.
(genestack) root@controller01:~# /opt/genestack/bin/install-postgres-operator.sh
/opt/genestack/submodules/postgres-operator/charts ~
Executing Helm command:
helm upgrade --install postgres-operator ./postgres-operator --version 1.12.2 --namespace=postgres-system --create-namespace --timeout 120m -f /opt/genestack/base-helm-configs/postgres-operator/postgres-operator-helm-overrides.yaml -f /etc/genestack/helm-configs/postgres-operator/postgres-operator-helm-overrides.yaml
Release "postgres-operator" has been upgraded. Happy Helming!
NAME: postgres-operator
LAST DEPLOYED: Wed Oct 8 03:03:56 2025
NAMESPACE: postgres-system
STATUS: deployed
REVISION: 2
TEST SUITE: None
NOTES:
To verify that postgres-operator has started, run:
kubectl --namespace=postgres-system get pods -l "app.kubernetes.io/name=postgres-operator"
~I was able to apply the custom helm overrides from /etc/genestack/helm-configs/postgres-operator/postgres-operator-helm-overrides.yaml