Orchestrator flavor installation using Helm
Install, configure, and manage the Orchestrator flavor in Red Hat Developer Hub using Helm
Abstract
1. Installing Red Hat Developer Hub with the Orchestrator on OpenShift using Helm
You can install Red Hat Developer Hub with Orchestrator on OpenShift Container Platform by using Helm, review resource requirements for Orchestrator, and plan for resource considerations in air-gapped environments.
1.1. Install the Orchestrator flavor using the Helm CLI
You can install the Orchestrator flavor of Red Hat Developer Hub (RHDH) on OpenShift using the Helm CLI. This method provides flexibility for custom configurations and automation. The Orchestrator flavor enables serverless workflows and orchestration capabilities.
You must be a cluster administrator to install the Orchestrator Helm chart because it deploys cluster-scoped resources. The Red Hat Developer Hub Helm chart may be installed by a user with namespace-level access.
Prerequisites
-
You are logged in to the OpenShift cluster using the
oc
CLI. - You have installed Helm and configured locally.
-
You have access to the official Red Hat container registry (
registry.redhat.io
). -
You have created a
values.yaml
file for the deployment. - You have access to the Red Hat Developer Hub Helm chart repository.
Procedure
Add the official OpenShift Helm charts repository:
helm repo add openshift-helm-charts https://charts.openshift.io/ helm repo update
Install the orchestrator infrastructure Helm chart:
helm install <release_name> openshift-helm-charts/redhat-developer-hub-orchestrator-infra
- Manually approve the install plans for OpenShift Serverless and Serverless Logic Operators. Wait until they are successfully deployed.
Install the Backstage chart with the orchestrator enabled:
helm install <release_name> openshift-helm-charts/redhat-developer-hub --version 1.7.0 \ --set orchestrator.enabled=true
(Optional) Disable the installation of the Serverless Logic and Serverless Operators if they are managed externally:
helm install <release_name> redhat-developer/backstage \ --set orchestrator.serverlessOperator=false \ --set orchestrator.serverlessLogicOperator=false
(Optional) Enable Notifications and Signals plugins by adding them under
global.dynamic.plugins
in yourvalues.yaml
file:global: dynamic: plugins: - disabled: false package: "./dynamic-plugins/dist/backstage-plugin-notifications" - disabled: false package: "./dynamic-plugins/dist/backstage-plugin-signals" - disabled: false package: "./dynamic-plugins/dist/backstage-plugin-notifications-backend-dynamic" - disabled: false package: "./dynamic-plugins/dist/backstage-plugin-signals-backend-dynamic"
(Optional) If using an external database, add the following configuration under
orchestrator.sonataflowPlatform
in yourvalues.yaml
file:orchestrator: sonataflowPlatform: externalDBsecretRef: "<cred-secret>" externalDBName: "<database_name>" externalDBHost: "<database_host>" externalDBPort: "<database_port>"
This only configures the Orchestrator’s use of an external database. To configure Red Hat Developer Hub to use an external PostgreSQL instance, follow the steps in: Configuring a PostgreSQL instance using Helm.
Verification
- Verify that the orchestrator plugin is visible in the Red Hat Developer Hub UI.
- Create and run sample workflows to confirm orchestration is functioning correctly.
Check the logs of the Orchestrator pod to verify workflow execution and plugin readiness. Use the following commands to check the Orchestrator pod logs:
# List pods in the namespace oc get pods -n <namespace> # Replace <orchestrator-pod-name> with the actual pod name oc logs -n <namespace> <orchestrator-pod-name>
(Optional) Stream logs in real-time:
oc logs -n <namespace> -f <orchestrator-pod-name>
1.2. Install the Orchestrator flavor using the OpenShift web console
You can install the Orchestrator flavor of Red Hat Developer Hub (RHDH) using the OpenShift Container Platform (OCP) web console. This method is useful if you prefer a graphical interface or want to deploy cluster-wide resources without using the Helm CLI.
You must be a cluster administrator to install the Orchestrator Helm chart because it deploys cluster-scoped resources.
Prerequisites
- You are logged in to the OpenShift Container Platform web console as a cluster administrator.
- You have access to the Red Hat Developer Hub Helm chart repository.
- Your cluster has internet access or the Helm charts are mirrored in a disconnected environment.
Procedure
- In the OpenShift web console, go to menu:Helm[Helm Charts].
- Click btn:[Repository] and confirm that the Red Hat Developer Hub Helm chart repository is available. If not, add it manually.
- Search for the Orchestrator Helm chart and click btn:[Install].
In the install form:
- Choose or create a target namespace.
- Accept or modify the default values as needed.
- Review and confirm the cluster-scoped resources that the chart will install.
- Click btn:[Install] to deploy the chart.
- Monitor the deployment status by navigating to menu:Workloads[Pods] or menu:Helm[Releases].
Verification
After deployment completes:
- The orchestrator-related pods should be running in the selected namespace.
- Cluster-wide resources such as CustomResourceDefinitions (CRDs) should be present.
- You can begin connecting the orchestrator to your Red Hat Developer Hub UI.