The default choice to write and deploy database migrations in Kubernetes is to wrap them in a Job. This approach has some drawbacks, and SchemaHero docs could explain this to help show the value in the operator approach.
- Transparency in debugging
- Sequencing
- Tightly coupling database migrations with an app migration
- ???
The default choice to write and deploy database migrations in Kubernetes is to wrap them in a Job. This approach has some drawbacks, and SchemaHero docs could explain this to help show the value in the operator approach.