Procedure

1. Download the plugin-infra.sh script as shown in the following example:

   curl -sSLO https://raw.githubusercontent.com/redhat-developer/rhdh-operator/refs/heads/release-${PRODUCT_VERSION}/config/profile/rhdh/plugin-infra/plugin-infra.sh # Specify the Red Hat Developer Hub version in the URL or use main

2. Run the script as shown in the following example:

   $ ./plugin-infra.sh

Procedure

1. To enable the Orchestrator plugin with default settings, set disabled: false for the package. For example, package: "@redhat/backstage-plugin-orchestrator@<plugin_version> is set to disabled: false:

   - package: "@redhat/backstage-plugin-orchestrator@<plugin_version>"
     disabled: false

Procedure

1. As an administrator, install relevant cluster-wide resources.

   helm repo add openshift-helm-charts https://charts.openshift.io/
   helm install <release_name> openshift-helm-charts/redhat-developer-hub-orchestrator-infra

   Important

   You must be an administrator to install the redhat-developer-hub-orchestrator-infra Helm chart because it deploys additional cluster-scoped OpenShift Serverless and OpenShift Serverless Logic Operators. As an administrator, you need to manually approve the install plans for OpenShift Serverless and Serverless Logic Operators.

2. Install the Backstage chart with the orchestrator enabled as shown in the following example:

   $ helm install <release_name> openshift-helm-charts/redhat-developer-hub --version 1.7.0 \
     --set orchestrator.enabled=true

3. (Optional) Enable Notifications and Signals plugins by adding them to the global.dynamic.plugins list in your values.yaml file as shown in the following example:

   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"

4. (Optional) You can disable the Serverless Logic and Serverless Operators individually or together by setting their values to false, as shown in the following example:

   helm install <release_name> openshift-helm-charts/redhat-developer-hub \
     --version 1.7.0 \
     --set orchestrator.enabled=true \
     --set orchestrator.serverlessOperator=false \
     --set orchestrator.serverlessLogicOperator=false

5. (Optional) If you are using an external database, add the following configuration under orchestrator.sonataflowPlatform in your values.yaml file:

   orchestrator:
     sonataflowPlatform:
       externalDBsecretRef: "<cred-secret>"
       externalDBName: "<database_name>" # The name of the user-configured existing database (Not the database that the orchestrator and sonataflow resources use).
       externalDBHost: "<database_host>"
       externalDBPort: "<database_port>"

   Note

   This step only configures the Orchestrators 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

1. Verify that the Orchestrator plugin is visible in the Red Hat Developer Hub UI.
2. Create and run sample workflows to confirm the orchestration is functioning correctly.

Procedure

1. In the OpenShift Container Platform web console, go to Helm → Helm Charts.
2. Click Repository and confirm that the Red Hat Developer Hub Helm chart repository is available.

3. Search for the Orchestrator infrastructure for Red Hat Developer Hub and click Install.

   Important

   You must be an administrator to install the Orchestrator Infrastructure for Red Hat Developer Hub Helm chart because it deploys cluster-scoped resources. As an administrator, you need to manually approve the install plans for OpenShift Serverless and Serverless Logic Operators.

   As a regular user, search for the Red Hat Developer Hub chart and install it by setting the value of orchestrator.enabled to true. Otherwise, the Orchestrator will not be deployed.

4. Wait until they are successfully deployed.
5. Monitor the deployment status by navigating to Workloads → Pods or Helm → Releases.

1. Default resource limits

1. You can override these values in any of the following ways:

   • With values.yaml
   • With --set flags

2. Override defaults with values.yaml as shown in the following example:

   orchestrator:
     enabled: true
     sonataflowPlatform:
     resources:
         limits:
           cpu: "500m"
           memory: "1Gi"

3. Override with --set as shown in the following example:

   helm upgrade --install <release_name>  openshift-helm-charts/redhat-developer-hub \
     --set orchestrator.enabled=true \
     --set orchestrator.sonataflowPlatform.resources.requests.cpu=500m \
     --set orchestrator.sonataflowPlatform.resources.requests.memory=128Mi \
     --set orchestrator.sonataflowPlatform.resources.limits.cpu=1 \
     --set orchestrator.sonataflowPlatform.resources.limits.memory=2Gi

   Note

   The --set setting is applicable only when orchestrator.enabled is true. By default, it is set to false.