Procedure

1. Create a pull secret in the olm namespace using the following command:

   kubectl -n olm create secret docker-registry rhdh-pull-secret \
       --docker-server=registry.redhat.io \
       --docker-username=<user_name> \ 1
       --docker-password=<password> \ 2
       --docker-email=<email> 3

   1

   Enter your username in the command.

   2

   Enter your password in the command.

   3

   Enter your email address in the command.

   The created pull secret is used to pull the Operator images from the Red Hat Ecosystem.

2. Create a CatalogSource resource in the olm namespace that contains the Operators from the Red Hat Ecosystem:

   cat <<EOF | kubectl -n olm apply -f -
   apiVersion: operators.coreos.com/v1alpha1
   kind: CatalogSource
   metadata:
     name: redhat-catalog
   spec:
     sourceType: grpc
     image: registry.redhat.io/redhat/redhat-operator-index:v4.17
     secrets:
     - "rhdh-pull-secret"
     displayName: Red Hat Operators
   EOF

3. Wait a few minutes until the Catalog Source is up and run the following command to list the available operators from the Red Hat ecosystem and confirm that the rhdh operator is listed:

   kubectl -n olm get packagemanifests

4. Create the rhdh-operator namespace aimed at containing the Operator:

   kubectl create namespace rhdh-operator

5. Create a pull secret in the rhdh-operator namespace:

   kubectl -n rhdh-operator create secret docker-registry rhdh-pull-secret \
       --docker-server=registry.redhat.io \
       --docker-username=<user_name> \ 1
       --docker-password=<password> \ 2
       --docker-email=<email> 3

   1

   Enter your username in the command.

   2

   Enter your password in the command.

   3

   Enter your email address in the command.

   The created pull secret is used to pull the Developer Hub images from the Red Hat Ecosystem.

6. Create an OperatorGroup resource as follows:

   cat <<EOF | kubectl apply -n rhdh-operator -f -
   apiVersion: operators.coreos.com/v1
   kind: OperatorGroup
   metadata:
     name: rhdh-operator-group
   EOF

7. Create a Subscription resource:

   cat <<EOF | kubectl apply -n rhdh-operator -f -
   apiVersion: operators.coreos.com/v1alpha1
   kind: Subscription
   metadata:
     name: rhdh
     namespace: rhdh-operator
   spec:
     channel: fast
     installPlanApproval: Automatic
     name: rhdh
     source: redhat-catalog
     sourceNamespace: olm
     startingCSV: rhdh-operator.v1.4.0
   EOF

8. Verify that the created Operator is running:

   kubectl -n rhdh-operator get pods -w

   If the operator pod shows ImagePullBackOff status, then you might need permissions to pull the image directly within the Operator deployment’s manifest.

   Tip

   You can include the required secret name in the deployment.spec.template.spec.imagePullSecrets list and verify the deployment name using kubectl get deployment -n rhdh-operator command:

   kubectl -n rhdh-operator patch deployment \
       rhdh-operator --patch '{"spec":{"template":{"spec":{"imagePullSecrets":[{"name":"rhdh-pull-secret"}]}}}}' \
       --type=merge

9. Update the default configuration of the operator to ensure that Developer Hub resources can start correctly using the following steps:

   1. Edit the backstage-default-config ConfigMap in the rhdh-operator namespace using the following command:

      kubectl -n rhdh-operator edit configmap backstage-default-config

10. Modify the default configuration of db-statefulset.yaml and deployment.yaml by adding the following fragment:

    securityContext:
      fsGroup: 300

    Following is the specified locations in the manifests:

    db-statefulset.yaml: | spec.template.spec
    deployment.yaml: | spec.template.spec

    1. Save and exit.

       Wait for a few minutes until the changes are automatically applied to the operator pods.

Procedure

1. Create an Image Pull Secret named rhdh-pull-secret using your Red Hat credentials to access images from the protected registry.redhat.io as shown in the following example:

   kubectl -n <your_namespace> create secret docker-registry rhdh-pull-secret \
       --docker-server=registry.redhat.io \
       --docker-username=<redhat_user_name> \
       --docker-password=<redhat_password> \
       --docker-email=<email>

2. Create an Ingress manifest file, named rhdh-ingress.yaml, specifying your Developer Hub service name as follows:

   apiVersion: networking.k8s.io/v1
   kind: Ingress
   metadata:
     name: rhdh-ingress
     namespace: <your_namespace>
   spec:
     ingressClassName: webapprouting.kubernetes.azure.com
     rules:
       - http:
           paths:
             - path: /
               pathType: Prefix
               backend:
                 service:
                   name: backstage-<your-CR-name>
                   port:
                     name: http-backend

3. To deploy the created Ingress, run the following command:

   kubectl -n <your_namespace> apply -f rhdh-ingress.yaml

4. Create a ConfigMap named app-config-rhdh containing the Developer Hub configuration using the following example:

   apiVersion: v1
   kind: ConfigMap
   metadata:
     name: app-config-rhdh
   data:
     "app-config-rhdh.yaml": |
       app:
         title: Red Hat Developer Hub
         baseUrl: https://<app_address>
       backend:
         auth:
           externalAccess:
               - type: legacy
                 options:
                   subject: legacy-default-config
                   secret: "${BACKEND_SECRET}"
         baseUrl: https://<app_address>
         cors:
           origin: https://<app_address>

5. Create a Secret named my-rhdh-secrets and add a key named BACKEND_SECRET with a Base64-encoded string value as shown in the following example:

   apiVersion: v1
   kind: Secret
   metadata:
     name: {my-product-secrets}
   stringData:
     BACKEND_SECRET: "xxx"

6. Create a Custom Resource (CR) manifest file named rhdh.yaml and include the previously created rhdh-pull-secret as follows:

   apiVersion: rhdh.redhat.com/v1alpha3
   kind: Backstage
   metadata:
     name: <your-rhdh-cr>
   spec:
     application:
       imagePullSecrets:
         - rhdh-pull-secret
       appConfig:
         configMaps:
           - name: "app-config-rhdh"
       extraEnvs:
         secrets:
           - name: "{my-product-secrets}"

7. Apply the CR manifest to your namespace:

   kubectl -n <your_namespace> apply -f rhdh.yaml