红帽全球峰会此内容没有您所选择的语言版本。
Chapter 5. 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
Backstagecustom resource. - If you used the Helm chart, set the replica values in the Helm configuration.
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
Backstagecustom resource (CR), setreplicasto a value greater than1.For example, to configure two replicas (one backup instance):
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
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
replicasto a value greater than1.For example, to configure two replicas (one backup instance):
upstream: backstage: replicas: 2upstream: backstage: replicas: 2Copy to Clipboard Copied! Toggle word wrap Toggle overflow
!:previouscontext:
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}