Repository navigation
Upgrade Keycloak from 15.1.1 to 19.02 on Kubernetes with AWS RDS(Postgres) #14682
sirishkumar
started this conversation in
Archive
Replies: 4 comments 9 replies
|
Its not even necessary to start with a single replica, Keycloak will lock the database while doing schema changes... |
5 replies
|
@sirishkumar how did the migration go, was the jump from 15 to 19 seamless, what docs helped.. what should one look out for? |
2 replies
|
One issue we observed was we have some issues on firefox, but after all cookies, it worked fine |
0 replies
|
I'm trying to upgrade the from 12.0.4 to 21.0.1 with a aws postgres db. But the migration keeps timing out after 5 mins and I can't figure out how to increase it. Any suggestions? |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi,
We have a Keycloak 15.1.1 deployment on Kubernetes with multiple replicas with the AWS RDS Postgres 13 Database backend. I did not find any upgrade guide or experience of other people regarding this setup or even with Kubernetes with Postgres using PVC upgrading Keycloak with multiple major version changes.
Does anyone have any experience with the Keycloak upgrade on Kubernetes?
I went through the change log and was able to run Keycloak locally using docker-compose only in HTTP mode as we terminate SSL at the reverse proxy.
From upgrade instructions from Keycloak documentation is the following strategy is the right one without losing any data
Update the docker image with a new image running only in HTTP mode in our helm charts
Initially start the new deployment with only a single replica so that the database schema changes are applied
kc.sh start --spi-connections-jpa-default-migration-strategy=updateRestart the deployment with
kc.sh start --optimizedAll reactions