Repository navigation
Replies: 2 comments 2 replies
|
Keycloak currently does not support zero-downtime upgrades. With the new map storage, this will be supported. |
|
Hello everyone! I apologize in advance if this is not the right place to ask my question, but I believe it is related to my investigation. We have started building our platform's authentication and authorization around Keycloak. As far as I understand, Keycloak releases updates frequently, so it would be nice if we could upgrade our production Keycloak cluster as quickly as possible. Like @andyc1864, we do not want to impact users during the upgrade process. However, we are hosting Keycloak on AWS ECS Fargate instead of Kubernetes and with AWS Aurora Postgres database. It would be very helpful if someone could point me to any related documentation or Github issues to watch for related functionality! What I've already found: Thank you in advance! |
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone.
I have a situation where I need to implement upgrades of services without impacting the end users. An approach we are using for a number of services is Blue/Green using separate namespaces in a Kubernetes cluster.
I need to cover off version upgrades for Keycloak and introducing them in a non-impacting way. Is there a process /method that anyone can help me with? I have read the upgrade documentation, but they all seem to depend on a cutover point which would have an impact on the end user.
We are currently running Keycloak in a Kubernetes cluster, and are using Infinispan.
Thanks for your time.
Andy
We
All reactions