Chapter 4. Installing RHTAP in your cluster

Procedure

1. In your CLI, create a new directory.

   $ mkdir tmp

2. Extract the install charts to your new directory. Replace $CONFIG with the path of the config.yaml file.

   Note

   You don’t need to add the --config parameter if you run the rhtap-cli installer command from a local clone of the rhtap-cli repo and you’re in the corresponding branch. In this case, RHTAP locates config.yaml automatically.

   $ rhtap-cli installer --extract=tmp --config="$CONFIG"

3. Create a copy of the config.yaml that now exists in that directory.

   $ cp tmp/config.yaml tmp/my-config.yaml

4. Using your preferred text editor, change the contents of the file as appropriate for the optional procedures you completed:

   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 integrated ACS or Quay, then change the values for the relevant enabled fields to false. The example below shows the change you need to make for ACS.

      redHatAdvancedClusterSecurity:
            enabled: false
            namespace: rhtap-acs

      Note

      If you try to integrate ACS or Quay but do not customize config.yaml, RHTAP still installs and uses new instances of those products. You must customize config.yaml for your rhtap-cli integration commands to take effect.

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

Procedure

1. In your CLI, 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.

   $ rhtap-cli deploy --config=$CONFIG

2. Once installation is complete, be sure to save the output of the rhtap-cli deploy command in your ~/install_values.txt 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…​.