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

Externalize validation database #19

Open
jefkel opened this issue Mar 14, 2019 · 0 comments
Open

Externalize validation database #19

jefkel opened this issue Mar 14, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@jefkel
Copy link
Contributor

jefkel commented Mar 14, 2019

Idea:

Separate the backup pod (whether job pod or long running pod) from the validation DB pod. This would allow a target DB to be customized without impacting build/deployments of backup pod. It would also allow the resources for a recovery test DB to be managed separately from the backup pod (specifically when the backup pod is using the long running option)

Details:

  • Validation DB pod deployment triggered from within backup pod
  • Default validation image from postgresql ephemeral image (easier cleanup, less resource consumption)
  • non-ephemeral customization options ? (for those DB's that are too large for ephemeral)
  • post validation cleanup to spin validation deployment down to 0 (releasing all resources, incl storage)
@jefkel jefkel changed the title Externalize recovery validation DB Externalize validation database Mar 14, 2019
@WadeBarnes WadeBarnes added the enhancement New feature or request label Mar 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants