Procedure

1. Connect to your GKE cluster using the following command:

   gcloud container clusters get-credentials <cluster-name> \ 1
       --location=<cluster-location> 2

   1

   Enter your GKE cluster name.

   2

   Enter your GKE cluster location.

   This command configures your Kubernetes client to point to your GKE cluster.

2. Run the following command in your terminal to create the rhdh-operator namespace where the Operator is installed:

   kubectl create namespace rhdh-operator

3. Create a pull secret using the following command:

   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.

4. Create a CatalogSource resource that contains the Operator from the Red Hat Ecosystem:

   Example CatalogSource resource

   cat <<EOF | kubectl -n rhdh-operator 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

5. Create an OperatorGroup resource as follows:

   Example OperatorGroup resource

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

6. Create a Subscription resource using the following code:

   Example 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: rhdh-operator
     startingCSV: rhdh-operator.v1.4.0
   EOF

7. Run the following command to verify that the created Operator is running:

   kubectl -n rhdh-operator get pods -w

   If the Operator pod shows ImagePullBackOff status, you might need permission 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. For example:

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

8. Update the default configuration of the Operator to ensure that Developer Hub resources can start correctly in GKE 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

   2. Locate the db-statefulset.yaml string and add the fsGroup to its spec.template.spec.securityContext, as shown in the following example:

      db-statefulset.yaml fragment

        db-statefulset.yaml: |
          apiVersion: apps/v1
          kind: StatefulSet
      --- TRUNCATED ---
          spec:
          --- TRUNCATED ---
            restartPolicy: Always
            securityContext:
            # You can assign any random value as fsGroup
              fsGroup: 2000
            serviceAccount: default
            serviceAccountName: default
      --- TRUNCATED ---

   3. Locate the deployment.yaml string and add the fsGroup to its specification, as shown in the following example:

      deployment.yaml fragment

        deployment.yaml: |
          apiVersion: apps/v1
          kind: Deployment
      --- TRUNCATED ---
          spec:
            securityContext:
              # You can assign any random value as fsGroup
              fsGroup: 3000
            automountServiceAccountToken: false
      --- TRUNCATED ---

   4. Locate the service.yaml string and change the type to NodePort as follows:

      service.yaml fragment

        service.yaml: |
          apiVersion: v1
          kind: Service
          spec:
           # NodePort is required for the ALB to route to the Service
            type: NodePort
      --- TRUNCATED ---

   5. Save and exit.

      Wait until the changes are automatically applied to the Operator pods.

Procedure

1. Go to your terminal and run the following command to add the Helm chart repository containing the Developer Hub chart to your local Helm registry:

   helm repo add openshift-helm-charts https://charts.openshift.io/

2. Create a pull secret using the following command:

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

   1

   Enter your GKE namespace in the command.

   2

   Enter your username in the command.

   3

   Enter your password in the command.

   4

   Enter your email address in the command.

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

3. Set up a Google-managed certificate by creating a ManagedCertificate object that you must attach to the ingress.

   Example of attaching a ManagedCertificate object to the ingress

   apiVersion: networking.gke.io/v1
   kind: ManagedCertificate
   metadata:
     name: <rhdh_certificate_name>
   spec:
     domains:
       - <rhdh_domain_name>

   For more information about setting up a Google-managed certificate, see Setting up a Google-managed certificate.

4. Create a FrontendConfig object to set a policy for redirecting to HTTPS. You must attach this policy to the ingress.

   Example of attaching a FrontendConfig object to the ingress

   apiVersion: networking.gke.io/v1beta1
   kind: FrontendConfig
   metadata:
     name: <ingress_security_config>
   spec:
     sslPolicy: gke-ingress-ssl-policy-https
     redirectToHttps:
       enabled: true

   For more information about setting a policy to redirect to HTTPS, see HTTP to HTTPS redirects.

5. Create a file named values.yaml using the following template:

   Example values.yaml file

   global:
     host: <rhdh_domain_name>
   route:
     enabled: false
   upstream:
     service:
       type: NodePort
     ingress:
       enabled: true
       annotations:
         kubernetes.io/ingress.class: gce
         kubernetes.io/ingress.global-static-ip-name: <ADDRESS_NAME>
         networking.gke.io/managed-certificates: <rhdh_certificate_name>
         networking.gke.io/v1beta1.FrontendConfig: <ingress_security_config>
       className: gce
     backstage:
       image:
         pullSecrets:
         - rhdh-pull-secret
       podSecurityContext:
         fsGroup: 2000
     postgresql:
       image:
         pullSecrets:
         - rhdh-pull-secret
       primary:
         podSecurityContext:
           enabled: true
           fsGroup: 3000
     volumePermissions:
       enabled: true

6. Run the following command in your terminal to deploy Developer Hub using the latest version of Helm Chart and using the values.yaml file:

   helm -n <your_namespace> install -f values.yaml <your_deploy_name> \
     openshift-helm-charts/redhat-developer-hub \
     --version 1.4.0

   For the latest Helm Chart version, see this Helm Charts repository.

   Note

   • To upgrade your deployment, use the following command:

     helm -n <your_namespace> upgrade -f values.yaml <your_deploy_name> openshift-helm-charts/redhat-developer-hub --version <UPGRADE_CHART_VERSION>

   • To delete your deployment, use the following command:

     helm -n <your_namespace> delete <your_deploy_name>