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

[Feat] Use a job for database migration #357

Open
sleipnir opened this issue Aug 8, 2024 · 0 comments
Open

[Feat] Use a job for database migration #357

sleipnir opened this issue Aug 8, 2024 · 0 comments
Assignees
Labels
Milestone

Comments

@sleipnir
Copy link
Member

sleipnir commented Aug 8, 2024

Describe the feature
Currently, each Pod performs a complete database migration. The proposal would be to transfer this responsibility to a Kubernetes Job that could, preferably, execute before the application pods are started. This way, only one migration execution would occur instead of n times as it happens today.

Why would that be important to you?
Avoids unnecessary migration runs and reduces proxy startup time.

@sleipnir sleipnir added the good first issue Good for newcomers label Aug 8, 2024
@sleipnir sleipnir moved this to Todo in Spawn v1.5.0 Aug 8, 2024
@sleipnir sleipnir removed this from Spawn v1.5.0 Sep 19, 2024
@sleipnir sleipnir added this to the 1.6.0 milestone Sep 19, 2024
@sleipnir sleipnir moved this to Ready in Spawn v1.6.0 Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Ready
Development

No branches or pull requests

2 participants