Red Hat Summit Red Hat Summitサポートコンソール開発者トライアルの開始お問い合わせ

このコンテンツは選択した言語では利用できません。

Chapter 6. Configuring high availability in Red Hat Developer Hub

High availability (HA) is a system design approach that ensures a service remains continuously accessible, even during failures of individual components, by eliminating single points of failure. It introduces redundancy and failover mechanisms to minimize downtime and maintain operational continuity.

Red Hat Developer Hub supports HA deployments on the following platforms:

  • Red Hat OpenShift Container Platform
  • Azure Kubernetes Service
  • Elastic Kubernetes Service
  • Google Kubernetes Engine

The HA deployments enable more resilient and reliable service availability across supported environments.

In a single instance deployment, if a failure occurs, whether due to software crashes, hardware issues, or other unexpected disruptions, it would make the entire service unavailable, interrupting development workflows and access to key resources.

With HA enabled, you can scale the number of backend replicas to introduce redundancy. This setup ensures that if one pod or component fails, others continue to serve requests without disruption. The built-in load balancer manages ingress traffic and distributes the load across the available pods. Meanwhile, the RHDH backend manages concurrent requests and resolves resource-level conflicts effectively.

As an administrator, you can configure high availability by adjusting replica values in your configuration file:

  • If you installed using the Operator, configure the replica values in your Backstage custom resource.
  • If you used the Helm chart, set the replica values in the Helm configuration.

6.1. Configuring high availability in a Red Hat Developer Hub Operator deployment
リンクのコピー

RHDH instances that are deployed with the Operator use configurations in the Backstage custom resource (CR). In the Backstage CR, the default value for the replicas field is 1. If you want to configure your RHDH instance for high availability, you must set replicas to a value greater than 1.

Procedure

  • In your Backstage custom resource (CR), set replicas to a value greater than 1.

    For example, to configure two replicas (one backup instance): 

    apiVersion: rhdh.redhat.com/v1alpha5
kind: Backstage
metadata:
  name: <your_yaml_file>
spec:
  deployment:
    patch:
      spec:
        replicas: 2
    Copy to Clipboard Toggle word wrap

6.2. Configuring high availability in a Red Hat Developer Hub Helm chart deployment
リンクのコピー

When you are deploying Developer Hub using the Helm chart, you must set replicas to a value greater than 1 in your Helm chart. The default value for replicas is 1.

Procedure

  • In your Helm chart configuration file, set replicas to a value greater than 1.

    For example, to configure two replicas (one backup instance): 

    upstream:
  backstage:
    replicas: 2
    Copy to Clipboard Toggle word wrap
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

Theme

© 2026 Red Hatトップに戻る