Chapter 3. Installing RHTAP in your cluster Once you have configured GitHub, you are ready to install RHTAP in your cluster. The actual installation process is quite simple. However, if you performed any of the optional procedures, you must also customize a file called config.yaml before installing RHTAP. This is not difficult, either. The following procedures explain how to complete both of these processes. 3.1. (Optional) Customizing config.yaml If you forked the software catalog, or ran optional integration commands, you should customize config.yaml , which is in the home directory of the installer. Customizing this file ensures that the RHTAP installer reacts correctly to the work you did in those procedures. Prerequisites A running installer container, which is logged in to your OCP cluster as ClusterAdmin. Procedure In the rhatp-cli container, create a copy of the config.yaml file:. Using the vi text editor, change the contents of /rhtap-cli/config.yaml as appropriate for the optional procedures you completed: If you forked the software catalog, then change the catalogURL to the URL for your fork, as shown in the example below. 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. 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. Once you have made the appropriate changes, save the new my-config.yaml file. 3.2. Installing RHTAP with the rhtap-cli deploy command If you have configured GitHub and, if necessary, customized config.yaml , then you are ready to install RHTAP. Prerequisites A running installer container, which is logged in to your OCP cluster as ClusterAdmin. None of the following operators are already installed in your cluster: Advanced Cluster Security AMQ Streams Crunch-Data PostgreSQL Developer Hub Keycloak OpenShift GitOps OpenShift Pipelines Quay Trusted Artifact Signer Procedure 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 USDCONFIG variable with the path of your customized file. Note Installation takes about fifteen minutes to complete. 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. Now, you can access your instance of RHTAP! 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. 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... .

Commands:
bash-5.1USD cp config.yaml my-config.yaml
bash-5.1USD vi my-config.yaml
redHatDeveloperHub: enabled: &rhdhEnabled true namespace: *installerNamespace properties: catalogURL: https://github.com/<your username>/tssc-sample-templates/blob/release/all.yaml
redHatAdvancedClusterSecurity: enabled: &rhacsEnabled false namespace: rhtap-acs
bash-5.1USD rhtap-cli deploy --config=USDCONFIG