Open TobiasJacob opened 2 years ago
I have forked the official timescaledb chart here: https://github.com/agronholm/timescaledb-kubernetes See the installation instructions there. This is one of the issues the fork seeks to resolve. Let me know if this resolved the problem for you.
Describe the bug The default values.yaml file sets empty credentials for AWS S3 buckets, that are passed to pgbackrest via environment variables. Unfortunately, they prevent setting up Azure backups, because (probably through a bug) as soon as pgbackrest finds an empty S3 environment variable, it starts complaining about it being empty, even when
repo1-type
is set to azure.To Reproduce Helm install with the following values:
Then pgbackrest does not work even though the repo type is set to azure.
The issue is caused by the empty env variables.
Adding this
to the values file does not update the secret anymore that induces the env variables into the stateful set when backups are setup after the initial deployment of timescaledb.
Expected behavior Setting the default
PGBACKREST_REPO1_S3_*
to null, instead of the empty string, or not setting them at all will not create empty environment variables in the container that cause a very misleading error message. It took me a while to figure out that the empty env variables caused pgbackrest to complain about S3 bucket credentials even though therepo1-type
was set toazure
.