Join us at KeycloakCon Japan 2026, colocated with KubeCon Japan 2026 · July 28 · Register Today →

Managing upgrades (v2)

How to manage multi-cluster upgrades
This guide is describing a feature which is currently in preview. Please provide your feedback by joining this discussion while we’re continuing to work on this.

This topic describes a highly available multi-cluster setup and the behavior to expect. It outlines the requirements of the high availability architecture and describes the benefits and tradeoffs. See Multi-cluster deployments (v2) for the introduction.

Keycloak upgrades

Patch upgrades can be deployed with zero-downtime.

Deploying different Keycloak major/minor versions on each of the sites is not supported. It is technically possible for upgrades to be rolled out to both sites simultaneously, however we recommend that upgrades be rolled out to one site at a time in order to simplify monitoring and debugging. Rollouts in the different sites should be done promptly to avoid older sites writing data that other sites assume to be already migrated.

For major or minor version upgrades:

  • Shut down all sites except one.

  • Deploy the new minor or major version in one site and verify the installation.

  • Deploy the new version in all other sites.

Database upgrades

Follow your database vendor’s zero-downtime upgrade procedure, and possibly combine it with a Keycloak upgrade.

On this page