Hi,
I want to know the case Standalone Clustered-HA work well when DB migration.
background
I’d migrate from postgreSQL10 to postgreSQL13 in KeyCloak7
each instance will stop and restart.
I want to know the case using Standalone Clustered-HA, DB connection change will not affect the KeyCloak data.(e.g not vanish the data in memory)
Standalone Clustered Mode is sharing the data in memory with every connected instance.
Does anyone have the case PostgreSQL DB migrtation in KeyCloak？
env
KeyCloak 7.0.1
PostgreSQL10 (on Azure database for postgreSQL single server)
PostgreSQL10 (on Azure database for postgreSQL flexible server)
migration steps( Assumption)
Before the migration:
KeyCloak7 on VM #1,#2,#3 → DB(postgreSQL10)
Step1:
Stop KeyCloak on Vm #1
change the connection KeyCloak on Vm #1 from postgreSQL10 to 13
Start KeyCloak on Vm #1
KeyCloak7 on VM #1 → DB(postgreSQL13)
KeyCloak7 on VM #2,3 → DB(postgreSQL10)
Step2:Stop KeyCloak on Vm #2
change the connection KeyCloak on Vm #2 from postgreSQL10 to 13
Start KeyCloak on Vm #2
KeyCloak7 on VM #1,2 → DB(postgreSQL13)
KeyCloak7 on VM #3 → DB(postgreSQL10)
Step3:Stop KeyCloak on Vm #3
change the connection KeyCloak on Vm #3 from postgreSQL10 to 13
Start KeyCloak on Vm #3
KeyCloak7 on VM #1,2,3 → DB(postgreSQL13)
After the migration:
KeyCloak7 on VM #1,#2,#3 → DB(postgreSQL13)