Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document choice of postgres operator #160

Merged
merged 1 commit into from
Oct 23, 2024
Merged

Document choice of postgres operator #160

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions docs/postgres-operator.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
Q: eoapi-k8s uses the postgres-operator from crunchydata. Is there a reason why you have chosen this solution? There is also a postgres-operator from Zalando. What are the benefits using an operator instead of a postgres helm chart?

A: We made the choice to use Crunchydata's operator over Zalando's operator and cloudnative-pg's operator (they all install operators even if using the helm install option) after considering the following things:

1. quality of the documentation
2. backlog of issues
3. knowing that a lot of core PG contributors work at Crunchydata and hearing about some of the cutting edge things they are doing
4. talking with other folks in our community

That said, what we want out of an operator "most" of the above options share:

1. backups
2. some kind of connection pooling option set up for us
3. good solid docs and choices about how upgrades work

See also https://github.com/developmentseed/eoapi-k8s/issues/132
Loading