zalando / zalando/postgres-operator
Unable to create timescaledb_toolkit extension using helm chart
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Hi guys, recently i try to deploy timescaledb using helm chart on k8s, but unfortunely i can't find the timescaledb_toolkit extension after installed
- Which image of the operator are you using?
- ghcr.io/zalando/postgres-operator:v1.14.0
- Where do you run it - cloud or metal? Kubernetes or OpenShift? [AWS K8s | GCP ... | Bare Metal K8s]
- Helm Chart Kubernetes
- Are you running Postgres Operator in production? [yes | no]
- yes
- Type of issue? [Bug report, question, feature request, etc.]
- Bug
apiVersion: "acid.zalan.do/v1"
kind: postgresql
metadata:
name: insight-timescaledb
namespace: insight-timescaledb
spec:
teamId: "insight"
volume:
size: 32Gi
numberOfInstances: 2
users:
insight: # db owner
- superuser
- createdb
databases:
foo: insight
preparedDatabases:
insight:
extensions:
timescaledb: public
timescaledb_toolkit: public
schemas:
public:
defaultRoles: false
postgresql:
version: "16"
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: "application"
operator: In
values:
- dependency
tolerations:
- key: "application"
operator: "Equal"
value: "dependency"
effect: "NoSchedule"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin with the Helm chart and the PostgreSQL manifest's preparedDatabases.extensions block, using the stated operator image and PostgreSQL 16 configuration. Reproduce the deployment and verify whether timescaledb_toolkit becomes available; done means the extension is present in the prepared database or the relevant chart or image limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100