Chapter 1. Provisioning and using your custom Red Hat Developer Hub configuration

Procedure

1. Author your custom <my_product_secrets>.txt file to provision your secrets as environment variables values in an OpenShift Container Platform secret, rather than in clear text in your configuration files. It contains one secret per line in KEY=value form.

   • Enter your authentication secrets.

2. Author your custom app-config.yaml file. This is the main Developer Hub configuration file.

   The baseUrl field is mandatory in your app-config.yaml file to ensure proper functionality of Developer Hub. You must specify the baseUrl in both the app and backend sections to avoid errors during initialization.

   Example 1.1. Configuring the baseUrl in app-config.yaml

   app:
     title: Red Hat Developer Hub
     baseUrl: https://<my_developer_hub_url>
   
   backend:
     auth:
       externalAccess:
         - type: legacy
           options:
             subject: legacy-default-config
             secret: "${BACKEND_SECRET}"
     baseUrl: https://<my_developer_hub_url>
     cors:
       origin: https://<my_developer_hub_url>

   Copy to Clipboard Toggle word wrap

   Optionally, enter your configuration such as:

   • Authentication in Red Hat Developer Hub.
   • Authorization in Red Hat Developer Hub.
   • Customization.
   • Configure your OpenShift Container Platform integration.

3. Provision your custom configuration files to your OpenShift Container Platform cluster.

   1. Create the <my-rhdh-project> project aimed at containing your Developer Hub instance.

      $ oc create namespace my-rhdh-project

      Copy to Clipboard Toggle word wrap

      Alternatively, create the project by using the web console.

   2. Provision your app-config.yaml file to the my-rhdh-app-config config map in the <my-rhdh-project> project.

      $ oc create configmap my-rhdh-app-config --from-file=app-config.yaml --namespace=my-rhdh-project

      Copy to Clipboard Toggle word wrap

      Alternatively, create the config map by using the web console.

   3. Provision your <my_product_secrets>.txt file to the <my_product_secrets> secret in the <my-rhdh-project> project.

      $ oc create secret generic <my_product_secrets> --from-file=<my_product_secrets>.txt --namespace=my-rhdh-project

      Copy to Clipboard Toggle word wrap

      Alternatively, create the secret by using the web console.

Procedure

1. Author your Backstage CR in a my-rhdh-custom-resource.yaml file to use your custom config maps and secrets.

   Example 1.2. Minimal my-rhdh-custom-resource.yaml custom resource example

   apiVersion: rhdh.redhat.com/v1alpha3
   kind: Backstage
   metadata:
     name: my-rhdh-custom-resource
   spec:
     application:
       appConfig:
         mountPath: /opt/app-root/src
         configMaps:
            - name: my-rhdh-app-config
       extraEnvs:
         secrets:
            - name: <my_product_secrets>
       extraFiles:
         mountPath: /opt/app-root/src
       replicas: 1
       route:
         enabled: true
     database:
       enableLocalDb: true

   Copy to Clipboard Toggle word wrap

   Example 1.3. my-rhdh-custom-resource.yaml custom resource example with dynamic plugins and RBAC policies config maps, and external PostgreSQL database secrets.

   apiVersion: rhdh.redhat.com/v1alpha3
   kind: Backstage
   metadata:
     name: <my-rhdh-custom-resource>
   spec:
     application:
       appConfig:
         mountPath: /opt/app-root/src
         configMaps:
            - name: my-rhdh-app-config
            - name: rbac-policies
       dynamicPluginsConfigMapName: dynamic-plugins-rhdh
       extraEnvs:
         secrets:
            - name: <my_product_secrets>
            - name: my-rhdh-database-secrets
       extraFiles:
         mountPath: /opt/app-root/src
         secrets:
           - name: my-rhdh-database-certificates-secrets
             key: postgres-crt.pem, postgres-ca.pem, postgres-key.key
       replicas: 1
       route:
         enabled: true
     database:
       enableLocalDb: false

   Copy to Clipboard Toggle word wrap

   Mandatory fields

   No fields are mandatory. You can create an empty Backstage CR and run Developer Hub with the default configuration.

   Optional fields

   spec.application.appConfig.configMaps

   Enter your config map name list.

   .Mount files in the my-rhdh-app-config config map.

   spec:
     application:
       appConfig:
         mountPath: /opt/app-root/src
         configMaps:
            - name: my-rhdh-app-config

   Copy to Clipboard Toggle word wrap

   Example 1.4. Mount files in the my-rhdh-app-config and rbac-policies config maps.

   spec:
     application:
       appConfig:
         mountPath: /opt/app-root/src
         configMaps:
            - name: my-rhdh-app-config
            - name: rbac-policies

   Copy to Clipboard Toggle word wrap

   spec.application.extraEnvs.envs

   Optionally, enter your additional environment variables that are not secrets, such as your proxy environment variables.

   Example 1.5. Inject your HTTP_PROXY, HTTPS_PROXY and NO_PROXY environment variables.

   spec:
     application:
       extraEnvs:
         envs:
           - name: HTTP_PROXY
             value: 'http://10.10.10.105:3128'
           - name: HTTPS_PROXY
             value: 'http://10.10.10.106:3128'
           - name: NO_PROXY
             value: 'localhost,example.org'

   Copy to Clipboard Toggle word wrap

   spec.application.extraEnvs.secrets

   Enter your environment variables secret name list.

   Example 1.6. Inject the environment variables in your Red Hat Developer Hub secret

   spec:
     application:
       extraEnvs:
         secrets:
            - name: <my_product_secrets>

   Copy to Clipboard Toggle word wrap

   Example 1.7. Inject the environment variables in the Red Hat Developer Hub and my-rhdh-database-secrets secrets

   spec:
     application:
       extraEnvs:
         secrets:
            - name: <my_product_secrets>
            - name: my-rhdh-database-secrets

   Copy to Clipboard Toggle word wrap

Procedure

1. Configure Helm to use your custom configuration files in Developer Hub.

   1. Go to the Helm tab to see the list of Helm releases.
   2. Click the overflow menu on the Helm release that you want to use and select Upgrade.
   3. Use the YAML view to edit the Helm configuration.

   4. Set the value of the upstream.backstage.extraAppConfig.configMapRef and upstream.backstage.extraAppConfig.filename parameters as follows:

      Helm configuration excerpt

      upstream:
        backstage:
          extraAppConfig:
            - configMapRef: my-rhdh-app-config
              filename: app-config.yaml

      Copy to Clipboard Toggle word wrap

   5. Click Upgrade.