Allow specifying additional volumes for pods via helm chart

[keithlayne]

Overview

I'd like to be able to specify additional volumes for the various cluster pods via the helm chart. I've run across multiple helm charts that use something like extraVolumes as a key in the values.

Now that sidecar containers can be easily configured for the database and pgBouncer pods, this would be a welcome improvement to make that feature more useful.

Use Case

My immediate use case is to allow mounting a ConfigMap for a pgBouncer sidecar container. I'd like to put my sidecar configuration there, and reload it with an additional sidecar. This is exactly how the pgBouncer pod works to avoid restarting the pod when config changes. I'd like to have the same flexibility with my sidecar container.

Desired Behavior

For example, add a proxy.pgBouncer.extraVolumes value and include it the volumes spec for that pod. This could additionally be valuable for any db sidecars.

Environment

• Platform: Kubernetes
• Platform Version: 1.30
• PGO Image Tag: ubi8-16.8-0
• Postgres Version: 16

[keithlayne]

The more I look at this the bigger a pain point this becomes. I need to generate config for my sidecar via helm template values. I'll probably end up scripting some kinda entrypoint that writes config directly into my db template, which should work, but is pretty rough.

[keithlayne]

Maybe I can co-opt this? https://access.crunchydata.com/documentation/postgres-operator/latest/references/crd/5.7.x/postgrescluster#postgresclusterspecproxypgbouncerconfigfilesindex

[keithlayne]

Ah, great, I was able to use proxy.pgbouncer.config.files to get a configmap included in the pgbouncer-config volume. This wasn't obvious though, and I'm meh about that getting mounted in the pgbouncer container. However, it's a solution, so I'm happy.

On the other hand, it may be handy to allow the extraVolumes thing if there's demand. Something to consider for the future.