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.

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

Add database persistent storage #189

Closed
askmeegs opened this issue May 21, 2020 · 1 comment
Closed

Add database persistent storage #189

askmeegs opened this issue May 21, 2020 · 1 comment
Labels
databases SQL database issues for accounts-db, ledger-db priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@askmeegs
Copy link
Collaborator

For in-cluster DBs.

@askmeegs askmeegs added what/feature New feature or request priority/P1 databases SQL database issues for accounts-db, ledger-db labels May 21, 2020
@askmeegs askmeegs modified the milestones: v0.4.0 - Observability, security, v0.5.0 - High availability, Anthos install profiles Jun 9, 2020
@askmeegs askmeegs removed this from the v0.5.0 - Test infra integration + kustomize profiles milestone Jun 21, 2020
@daniel-sanche
Copy link
Member

We use stateful sets, so it should be pretty easy to attach a storage volume, but so far I've held back for compatibility reasons (we don't want a hard dependency on GCP, don't want to worry about local storage differences between minikube/kind, don't want to have to deal with bugs that arise when deploying new versions over existing data...).

If we're getting requests to add storage, I'd suggest doing it in a kustomize overlay so the default deployment stays simple. Or when we add CloudSQL that will store persistently by default, so it might just be better to just show CloudSQL when we want to tell that story

@JustinBeckwith JustinBeckwith added priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. and removed priority/P1 what/feature New feature or request labels Oct 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
databases SQL database issues for accounts-db, ledger-db priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

3 participants