Timescaledb-single helm chart fails to launch because could not access timescaledb_toolkit

[theelderbeever]

What happened? I am installing a a helm release of the timescale-single on an EKS cluster with amd64 nodes. The values.yaml has timescaledb_toolkit in the autoload libraries which has been fine in the past. Recently, on the timescaledb-ha:pg14-latest (pg14-2.8) the release will fail to start the timescaledb pod due to the following error...

FATAL: could not access file "timescaledb_toolkit": No such file or directory

Did you expect to see something different? In the past this hasn't been an error. Additionally, if you remove it from the autoload libraries and manually create the extension after deployment the file does exist.

How to reproduce it (as minimally and precisely as possible): Launch the latest helm chart?

Environment

• Which helm chart and what version are you using? timescaledb-single REVISION: 1

• What is in your values.yaml ? Its this line that causes the issue. patroni.dcs.postgresql.shared_preload_libraries: timescaledb,timescaledb_toolkit,pg_stat_statements

• Kubernetes version information:

  kubectl version

Server Version: version.Info{Major:"1", Minor:"23+", GitVersion:"v1.23.7-eks-4721010" Also tested on Ubuntu 22.04 microk8s 1.25

• Kubernetes cluster kind:

  EKS and Microk8s both tested

Anything else we need to know?:

[agronholm]

There is no timescaledb_toolkit in the default values: https://github.com/timescale/helm-charts/blob/main/charts/timescaledb-single/values.yaml#L207 Did you add it yourself? Also, there is no v1 of the chart available. The latest release is v0.15.0.

[theelderbeever]

Sorry it is version 0.15. The output of chart ends up saying REVISION 1.

I didn't build the extension myself however, after creating a database you can run CREATE EXTENSION timscaledb_toolkit; and it installs properly. I have run previous versions of the chart and was able to have it preload just fine. Seems to only be after I updated my helm repo with the latest chart. I can try and do some more footwork and see what version it mights have diverged.

[agronholm]

This sounds like the extension is missing from the image. Does this issue then not belong in the timescaledb-docker-ha tracker?

[theelderbeever]

It might still belong there but the extension does exist because I don't have to build it or anything once the chart is deployed. I can just create it.