Skip to content
This repository has been archived by the owner on Mar 14, 2020. It is now read-only.

Figure out strategy for database migration #303

Open
Tracked by #297
mcritchlow opened this issue Oct 4, 2019 · 0 comments
Open
Tracked by #297

Figure out strategy for database migration #303

mcritchlow opened this issue Oct 4, 2019 · 0 comments

Comments

@mcritchlow
Copy link
Member

Descriptive summary

When we deploy High Five into k8s, we're going to presumably no longer use the current production database (though we should talk about that)

Under that assumption, we will need a plan for migrating data from the current production database to the new database managed in k8s.

Rationale

When we move the application to k8s we want to do so with no interruption or data loss for current users.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant