Can anyone point me to any best practices on running database migrations in a kubernetes (or similar) environment with automated deployment?
Follow
@Floppy More important question: do you *really* want to auto-deploy this? If we're talking SQL, we're talking exclusive lock. Which is super-happy fun times. Waits for anything currently using the table to finish, but while waiting causes all new queries to wait. Those queries may take locks on other tables. Setting statement timeout would deal with some of that, maybe.
