이 콘텐츠는 선택한 언어로 제공되지 않습니다.

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

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

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

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

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

맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat