zalando / zalando/postgres-operator
extension uuid-ossp installation in database cluster
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Hi I tried to configure extension uuid-ossp in database yml https://github.com/zalando/postgres-operator/blob/master/manifests/minimal-postgres-manifest.yaml but when the cluster was created I don't see the extension installed in postgres default database
Is something missing below here or below one is the right way to configure this extension.
apiVersion: "acid.zalan.do/v1"
kind: postgresql
metadata:
name: acid-minimal-cluster
namespace: default
spec:
teamId: "acid"
volume:
size: 1Gi
numberOfInstances: 2
users:
zalando: # database owner
- superuser
- createdb
foo_user: [] # role for application foo
databases:
foo: zalando # dbname: owner
preparedDatabases:
bar:
defaultUsers: true
extensions:
uuid-ossp: public
postgresql:
version: "12"
/shiv
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
Start with manifests/minimal-postgres-manifest.yaml and the preparedDatabases configuration shown in the report. Check how the operator handles uuid-ossp for the prepared database bar versus PostgreSQL's default database, then reproduce cluster creation with PostgreSQL 12. Done means the extension appears in the expected database or the configuration limitation is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100