이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 4. 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 forked the software catalog, or if you integrated ACS or Quay, you must first customize a file called config.yaml
. This is also not difficult.
The following procedures explain how to complete both of these processes.
4.1. (Optional) Customizing config.yaml
If you forked the software catalog, or if you integrated ACS or Quay, you should customize the config.yaml
. Customizing this file ensures that the RHTAP installer reacts correctly to the work you did for those procedures.
Procedure
In your CLI, create a new directory.
$ mkdir tmp
Extract the install charts to your new directory. Replace $CONFIG with the path of the
config.yaml
file.NoteYou don’t need to add the
--config
parameter if you run therhtap-cli installer
command from a local clone of the rhtap-cli repo and you’re in the corresponding branch. In this case, RHTAP locatesconfig.yaml
automatically.$ rhtap-cli installer --extract=tmp --config="$CONFIG"
Create a copy of the
config.yaml
that now exists in that directory.$ cp tmp/config.yaml tmp/my-config.yaml
Using your preferred text editor, change the contents of the file 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.redHatDeveloperHub: enabled: &rhdhEnabled true namespace: *installerNamespace properties: catalogURL: https://github.com/<your username>/tssc-sample-templates/blob/release/all.yaml
If you integrated ACS or Quay, then change the values for the relevant
enabled
fields tofalse
. The example below shows the change you need to make for ACS.redHatAdvancedClusterSecurity: enabled: false namespace: rhtap-acs
NoteIf 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 customizeconfig.yaml
for yourrhtap-cli integration
commands to take effect.
-
Once you have made the appropriate changes, save the new
my-config.yaml
file.
4.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
- You must have logged in to your OCP cluster as ClusterAdmin.
You must ensure that none of the following operators are already installed in your cluster:
- AMQ Streams
- Crunch-Data PostgreSQL
- OpenShift GitOps
- Keycloak
- OpenShift Pipelines
- Trusted Artifact Signer
- Quay
- Advanced Cluster Security
- Developer Hub
Procedure
In your CLI, run the installation command. If you did not make any changes to
config.yaml
, you can simply runrhtap-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.NoteInstallation takes about fifteen minutes to complete.
$ rhtap-cli deploy --config=$CONFIG
-
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. 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…
.