We are currently using liquibase combined with db2i (using the liquibase-db2i extension) in a kubernetes environment. Recently, we came across using-liquibase-in-kubernetes and using-liquibase-and-docker which suggests running the liquibase changes in a separate init-container to minimize the possibility for database locks to get stuck because of a container doing the liquibase changes being shutdown while it has an active lock.