Repository navigation
|
Is there a guide or a suggested method for operating Keycloak through the Operator (kubectl) with a need for Manual migration strategy for the DB during updates ? |
Replies: 1 comment
|
The Operator doesn't really have a built-in "manual migration" mode. When you update the Keycloak CR with a new image version, the Operator will spin up the new version and KC automatically runs If you want to control migrations manually, you'd probably want to:
The catch is the Operator might restart the pod and KC will complain if the schema doesn't match what it expects. So timing matters — run the migration right before updating the CR. Some people just skip the Operator for upgrades and do it via direct StatefulSet manipulation when they need that level of control. The Operator is great for day-to-day operations but can be limiting for complex upgrade flows. |
The Operator doesn't really have a built-in "manual migration" mode. When you update the Keycloak CR with a new image version, the Operator will spin up the new version and KC automatically runs
--spi-connections-jpa-default-migration-strategy=update(Liquibase auto-migration) by default.If you want to control migrations manually, you'd probably want to:
--spi-connections-jpa-default-migration-strategy=manualon your KC instancekc.sh exportor directly run Liquibase against your DBThe catch is the Operator might restart the pod and KC will complain if the schema do…