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

Jump to bottom

Make cms-db highly available #3

Open
mrzzy opened this issue Mar 28, 2020 · 0 comments
Open

Make cms-db highly available #3

mrzzy opened this issue Mar 28, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@mrzzy
Copy link
Collaborator

mrzzy commented Mar 28, 2020 •
edited
Loading

Currently k8s-cms uses a in house cms-db image as its central database that all k8s-cms services depend on, directly or indirectly. This means that the database is k8s-cms's central point of failure.

Possible solution: Postgres has some database replication functionality that would let us replicate the database into multiple fail over instances. HA is available via Postgres helm charts.
@mrzzy mrzzy added the enhancement New feature or request label Mar 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mrzzy