Configuration and Documentation to run TimescaleDB in your Kubernetes cluster
Apache License 2.0
263
stars
223
forks
source link
Chart `timescaledb-single:` `pgbackrest --stanza=poddb stanza-create` blocked due to non existent `repo1-path` directory (in the container) when `repo1-path`'s name is auto generated #545
With the curent statefulset-timescaledb.yaml and auto generated repo1-path name, it seems there is no way (yet) to create the repo1-path directory some other way:
bootstrap script is not extensible via config.
mounting an additional volume in the pgbackrest container is not supported (yet ?)
mkdir -pv <repo1-path> within the container fails due to missing permission.
However, one can configure repo1-path to /scripts/poddb and create /scripts/poddb manually in the pgbackrest container. Then stanza creation succeeds and backups too.
Did you expect to see something different?
repo1-path directory is created automatically by the pgbackrest_bootstrap.sh script when non existent.
How to reproduce it (as minimally and precisely as possible):
What happened?
1. Context
With pgbackrest enabled,
repo1-path
(the path to store pgbackrest backups) is automatically set from configmap-pgbackrest.yaml via:2. Runtime
Once the
pgbackrest
container starts, it executespgbackrest_bootstrap.sh
and eventually run the pgbackrest --stanza=poddb stanza-create.However,
pgbackrest --stanza=poddb stanza-create
stays stuck (at least in our deployment).pgbackrest's user guide doc did manually create the repo1-path. Hence, it seems reasonable for this chart to create it too.
3. Workaround
With the curent
statefulset-timescaledb.yaml
and auto generatedrepo1-path
name, it seems there is no way (yet) to create therepo1-path
directory some other way:mkdir -pv <repo1-path>
within the container fails due to missing permission.However, one can configure
repo1-path
to/scripts/poddb
and create/scripts/poddb
manually in the pgbackrest container. Then stanza creation succeeds and backups too.Did you expect to see something different?
repo1-path
directory is created automatically by the pgbackrest_bootstrap.sh script when non existent.How to reproduce it (as minimally and precisely as possible):
Explained above.
Environment
Which helm chart and what version are you using? timescaledb-single-0.27.4
What is in your
values.yaml
? N/AKubernetes version information: k8s 1.23.x
Kubernetes cluster kind: Follow k8s official website instruction.
Anything else we need to know?: N/A