Use Cloud Native Postgres instead of bitnami
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.1k
- Forks
- 194
- Avg merge
- 18m
- Merged PRs (30d)
- 3
Description
I tried to pull up Tianji just to check it, but I have seen by default it tries to pull a bitnami postgresql image
Normal BackOff 3s (x9 over 2m35s) kubelet Back-off pulling image "docker.io/bitnami/postgresql:16.3.0-debian-12-r10"
It would be better if you could assume CloudNative PG is present in the cluster, and use a CNPG instance... CNPG is nowadays the de-facto way to run Postgres.
Contributor guide
No contributing guide indexed for this repository
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
No file, test, or entry point is named. Start by locating the Kubernetes deployment configuration and checking how the Bitnami PostgreSQL image is selected; then review the expected CloudNativePG instance setup. Done means Tianji deploys against the CNPG instance without pulling the Bitnami image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100