Red Hat Summit Red Hat SummitSuporteConsoleDesenvolvedoresComeçar um testeContato

Este conteúdo não está disponível no idioma selecionado.

Chapter 5. Configuring high availability in Red Hat Developer Hub

Previously, Red Hat Developer Hub supports a single-instance application. With this configuration, if the instance fails due to software crashes, hardware issues, or other unexpected disruptions, the entire Red Hat Developer Hub service becomes unavailable, preventing the development workflows or access to the resources. With high availability, you receive a failover mechanism that ensures the service is available even if one or more components fail. By increasing the number of replicas, you introduce redundancy to help increase higher productivity and minimize disruption.

As an administrator, you can configure high availability in Red Hat Developer Hub. Once you set the high availability option in Developer Hub, the Red Hat OpenShift Container Platform built-in Load Balancer manages the ingress traffic and distributes the load to each pod. The RHDH backend also manages concurrent requests or conflicts on the same resource.

You can configure high availability in Developer Hub by scaling your replicas to a number greater than 1 in your configuration file. The configuration file that you use depends on the method that you used to install your Developer Hub instance. If you used the Operator to install your Developer Hub instance, configure the replica values in your Backstage custom resource. If you used the Helm chart to install your Developer Hub instance, configure the replica values in your Helm chart.

5.1. Configuring High availability in a Red Hat Developer Hub Operator deployment
Copiar o link

RHDH instances that are deployed with the Operator use configurations in the Backstage custom resource. In the Backstage custom resource, 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, set replicas to a value greater than 1. For example: 

    apiVersion: rhdh.redhat.com/v1alpha3
kind: Backstage
metadata:
  name: <your_yaml_file>
spec:
  application:
    ...
    replicas: <replicas_value>
    1 
    
    ...
    Copy to Clipboard Toggle word wrap
    1
    Set the number of replicas based on the number of backup instances that you want to configure.

5.2. Configuring high availability in a Red Hat Developer Hub Helm chart deployment
Copiar o link

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

To configure your Developer Hub Helm chart for high availability, complete the following step:

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

    upstream:
  backstage:
    replicas: <replicas_value>
    1
    Copy to Clipboard Toggle word wrap
    1
    Set the number of replicas based on the number of backup instances that you want to configure.
Voltar ao topo
Red Hat logoGithubredditYoutubeTwitter

Aprender

Experimente, compre e venda

Comunidades

Sobre a documentação da Red Hat

Ajudamos os usuários da Red Hat a inovar e atingir seus objetivos com nossos produtos e serviços com conteúdo em que podem confiar. Explore nossas atualizações recentes.

Tornando o open source mais inclusivo

A Red Hat está comprometida em substituir a linguagem problemática em nosso código, documentação e propriedades da web. Para mais detalhes veja o Blog da Red Hat.

Sobre a Red Hat

Fornecemos soluções robustas que facilitam o trabalho das empresas em plataformas e ambientes, desde o data center principal até a borda da rede.

Theme

© 2025 Red Hat