Chapter 3. Installing RHTAP in your cluster

Procedure

1. In the rhatp-cli container, create a copy of the config.yaml file:.

   bash-5.1$ cp config.yaml my-config.yaml

2. Using the vi text editor, change the contents of /rhtap-cli/config.yaml as appropriate for the optional procedures you completed:

   bash-5.1$ vi my-config.yaml

   1. If you forked the software catalog, then change the catalogURL to the URL for your fork, as shown in the example below.

      redHatDeveloperHub:
            enabled: &rhdhEnabled true
            namespace: *installerNamespace
            properties:
              catalogURL: https://github.com/<your username>/tssc-sample-templates/blob/release/all.yaml

   2. If you ran rhtap-cli integration commands, then change the values for the relevant enabled fields to false. This is not necessary if you are using an alternative host for your source code. But any other integration you made requires a change to be made in this file. The example below shows the change you need to make for integrating a pre-existing instance of ACS.

      redHatAdvancedClusterSecurity:
            enabled: &rhacsEnabled false
            namespace: rhtap-acs

      Note

      If you try to integrate outside products or pre-existing instances, but do not customize config.yaml, RHTAP still installs and uses its default products. You must customize config.yaml for your rhtap-cli integration commands to take effect.

3. Once you have made the appropriate changes, save the new my-config.yaml file.

Procedure

1. In the rhatp-cli container, run the installation command. If you did not make any changes to config.yaml, you can simply run rhtap-cli deploy. But if you did customize that file, run the following command, and replace the $CONFIG variable with the path of your customized file.

   Note

   Installation takes about fifteen minutes to complete.

   bash-5.1$ rhtap-cli deploy --config=$CONFIG

2. Once installation is complete, be sure to save the output of the rhtap-cli deploy command in your private.env file. This output enables you to access your instances of the new products that are now installed.

3. Now, you can access your instance of RHTAP!

   1. After creating a GitHub app, you may have left the page for your new GitHub app open, as our note suggested. In that case, you can use the link in the banner of that page to access RHTAP.
   2. Otherwise, navigate to your the Authorized GitHub Apps tab on your Applications page. Click on the name of the app you created for RHTAP. Again, in the banner of this page, you can find the link you need to access RHTAP, which begins with https://backstage-developer-hub-rhtap…​.