Chapter 3. Pre-installation configuration

Procedure

1. In a browser, log in to GitHub.
2. Click your profile picture and select Settings.
3. Select Developer settings.
4. Select Personal access tokens.
5. Click Generate new token Generate new token(classic).

6. In the Select scopes: section, enable the following:

   • repo
   • read:org
   • workflow (as needed)
7. Click Generate token.
8. Save the personal access token.

Procedure

1. In a browser, log in to Gitlab and click your avatar.
2. Select Edit profile.
3. Select Access tokens.
4. Click Add new token.
5. Provide a name and expiration date for the token.

6. In the Scopes: section, select the following:

   • read_repository
   • api
7. Click Create personal access token.
8. Save the personal access token.

Procedure

1. In a browser, log in to the OpenShift Container Platform web console.

2. Creating a project varies slightly depending on which perspective you have on:

   1. From the Developer perspective: select Project then Create Project.
   2. From the Administrator perspective: select Home then Project then Create Project.

3. In the Create Project dialog box, enter a unique name Name field.

   • Lowercase alphanumeric characters (a-z, 0-9) and the hyphen character (-) are permitted for project names.
   • The underscore (_) character is not permitted.

   • The maximum length for project names is 63 characters.

     1. Optional: display name and description for your project.
4. Click Click to create the project.

Procedure

1. In a terminal, log in to OpenShift Container Platform using your credentials:

   oc login <OpenShift_API_URL> -u <username>

   The following example shows the output for a successful login:

   $ oc login https://api.<my_cluster>.com:6443 -u kubeadmin
   WARNING: Using insecure TLS client config. Setting this option is not supported!
   
   Console URL: https://api.<my_cluster>.com:6443/console
   Authentication required for https://api.<my_cluster>.com:6443 (openshift)
   Username: kubeadmin
   Password:
   Login successful.
   
   You have access to 22 projects, the list has been suppressed. You can list all projects with 'oc projects'
   
   Using project "default".

2. Create a new project. Use a unique project name.

   $ oc new-project <self-service-project-name>

   • Lowercase alphanumeric characters (a-z, 0-9) and the hyphen character (-) are permitted for project names.
   • The underscore (_) character is not permitted.

   • The maximum length for project names is 63 characters.

     Example:

     $ oc new-project <my-project>
     
     Now using project "my-project" on server "https://openshift.example.com:6443".

3. Open your new project:

   $ oc project <self-service-project-name>

Procedure

1. Create an auth.json file on your local machine.

2. Add the following structure to the auth.json file:

   {
     "auths": {
       "registry.redhat.io": {
         "auth": "<base64-encoded-username-password>"
       }
     }
   }

3. Generate the base64-encoded authentication value:

   printf '%s' '<username>:<password>' | base64 -w0

4. Replace <base64-encoded-username-password> in the auth.json file with the output from the previous step.

5. Create the authentication secret in the target OpenShift project. The secret name must match your Helm release name.

   If you install from the OpenShift catalog and you use the default release name redhat-rhaap-portal:

   oc create secret generic redhat-rhaap-portal-dynamic-plugins-registry-auth \
     --from-file=auth.json=./auth.json

   If you use a custom release name:

   oc create secret generic <release-name>-dynamic-plugins-registry-auth \
     --from-file=auth.json=./auth.json

1. In the OpenShift web console, select the OpenShift project where you will install the Helm release.
2. In the Administrator view, click Workloads Secrets.
3. Click Create Key/value secret.
4. Set the secret name to <release-name>-dynamic-plugins-registry-auth.
5. Add a key named auth.json and paste the contents of your auth.json file as the value.
6. Click Create.

1. In the Developer view, click Helm.
2. Select the Helm release.
3. Click Actions Upgrade.
4. In the YAML view, set redhat-developer-hub.global.pluginMode to oci (OCI container delivery) or tarball (HTTP plug-in registry).
5. Click Upgrade.

Procedure

1. Log in to your OpenShift Container Platform instance.
2. Open your OpenShift project for self-service automation portal in the Administrator view.
3. Click Secrets in the side pane.
4. Click Create to open the form for creating a new secret.
5. Select the Key/Value option.

6. Create a secret named secrets-rhaap-portal.

   Note

   The secret must use this exact name.

7. Add the following key-value pairs to the secret.

   Note

   The secrets must use the exact key names specified below.

   • Key: aap-host-url

     Value needed: Ansible Automation Platform instance URL

   • Key: oauth-client-id

     Value needed: Ansible Automation Platform OAuth client ID

   • Key: oauth-client-secret

     Value needed: Ansible Automation Platform OAuth client secret value

   • Key: aap-token

     Value needed: Token for Ansible Automation Platform user authentication (must have read access).

8. Click Create to create the secret.

Procedure

1. Log in to your OpenShift Container Platform instance.
2. Open your OpenShift project for self-service automation portal.
3. Click Secrets in the side pane.
4. Click Create to open the form for creating a new secret.
5. Select the Key/Value option.

6. Create a secret named secrets-scm.

   Note

   The secret must use this exact name.

7. Add the following key-value pairs to the secret. If you are only using one SCM, just add the key-value pair for that SCM.

   Note

   The secrets must use the exact key names specified below.

   • Key: github-token

     Value needed: Github Personal Access Token (PAT)

   • Key: gitlab-token

     Value needed: Gitlab Personal Access Token (PAT)

8. Click Create to create the secret.