Red Hat Summit Red Hat SummitSupportConsoleDéveloppeursCommencer un essaiContact

Ce contenu n'est pas disponible dans la langue sélectionnée.

Chapter 1. High availability overview

Explore the different Red Hat build of Keycloak high-availability architectures.

Red Hat build of Keycloak can be deployed in a number of high-availability architectures, allowing system administrators to pick the deployment type most suitable for their needs. Ease of deployment, cost and fault-tolerance guarantees are important considerations when determining the correct architecture for your deployments.

Any Red Hat build of Keycloak deployment must be installed on a properly configured OpenShift cluster that has been configured per the OpenShift installation instructions. For any Red Hat build of Keycloak installations on OpenShift clusters that span multiple sites (i.e. single cluster or multi-clusters across multiple availability zones) the OpenShift cluster must adhere to the Guidance for Red Hat OpenShift Container Platform Clusters.

Ultimately high availability architectures involve many components in addition to the software running and the responsibility for availability of the service is with the customer. This guide has recommended practices for using the Red Hat build of Keycloak in such high availability architectures.

1.1. Architectures
Copier lien

This document describes two high availability architectures in which to deploy Red Hat build of Keycloak: Single-cluster deployments and multi-cluster deployments.

1.1.1. Single-cluster deployments
Copier lien

Deploy Red Hat build of Keycloak in a single cluster, optionally across multiple availability-zones or data centers with the required network latency and database configuration, using Single-cluster deployments.

Advantages
  • No external dependencies
  • Deployment in a single OpenShift cluster
  • Tolerate availability-zone failure or data center failure, if deployed to multiple availability zones or data centers
Disadvantages

  • OpenShift cluster is a single point of failure:

    • Control-plane failures could impact all Red Hat build of Keycloak pods

1.1.2. Multi-cluster deployments
Copier lien

Connect two Red Hat build of Keycloak clusters deployed for example in different OpenShift clusters in two availability zones or data centers with the required network latency and database configuration using Multi-cluster deployments.

Advantages
  • Tolerate availability-zone failure
  • Tolerate OpenShift cluster failure
  • Bridge two networks that do not offer transparent networking
  • Regulatory compliance when distinct deployments are required
Disadvantages

  • Complexity:

    • External load-balancer required
    • Separate Data Grid cluster required on each site

  • Cost:

    • Additional load-balancer required
    • Additional compute is required for external Data Grid clusters
    • Two OpenShift control-planes must be provisioned
  • Not supported with three or more availability zones

1.1.3. Next Steps
Copier lien

To learn more about the different high-availability architectures and their supported configurations, please consult the individual chapters.

Retour au début
Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Theme

© 2025 Red Hat