From 17547340d42db38a0bca7bca934b01964991301b Mon Sep 17 00:00:00 2001 From: Krzysztof Opasiak Date: Tue, 10 Mar 2020 23:53:31 +0100 Subject: [COMMON] Allow special characters in postgress passwords Postgres image that we are currently using uses sed to replace passwords placeholders with their actual values at startup time. This apprach is very fragile and leads to issues if & happens to be a part of password as it has a special meaning in sed. To fix this issue let's just extract the setup.sql file from the container and process it on our own in init container using envsubst and then mount it to the main container to be used. Issue-ID: OOM-2317 Signed-off-by: Krzysztof Opasiak Change-Id: Ifd51d8f0af0099958caa209185fb7a87a0480bd2 --- kubernetes/common/postgres/values.yaml | 3 +++ 1 file changed, 3 insertions(+) (limited to 'kubernetes/common/postgres/values.yaml') diff --git a/kubernetes/common/postgres/values.yaml b/kubernetes/common/postgres/values.yaml index 7aff189ba9..10f9405de6 100644 --- a/kubernetes/common/postgres/values.yaml +++ b/kubernetes/common/postgres/values.yaml @@ -21,6 +21,9 @@ global: readinessRepository: oomk8s readinessImage: readiness-check:2.0.0 + # envsusbt + envsubstImage: dibi/envsubst + ################################################################# # Secrets metaconfig ################################################################# -- cgit 1.2.3-korg