Chapter 3. Integrating instances of ACS, Quay, Jenkins


RHTAP installs a network of products that work together to form a secure, automated CI/CD platform. However, there are two products—​Advanced Cluster Security (ACS) and Quay—​that you may integrate into RHTAP, rather than installing them as a part of RHTAP. If you already have instances of these products, integrating them saves time and prevents data loss. If you have instances of these products in your cluster and do not integrate them, then the installer just creates new instances in new namespaces.

Additionally, RHTAP uses Tekton by default to define and run build pipelines for your applications. However, you can also integrate Jenkins, to use it as the basis for your build pipeline instead.

The following procedures explain how to integrate each of these products into RHTAP—​ACS, Quay, and Jenkins.

3.1. Integrating ACS

Prerequisites

  • Administrator access to an instance of ACS.

Procedure

  1. Before you can integrate your instance of ACS, you need an API token and the central endpoint URL.

    1. Follow the instructions for the prerequisites here to create an API token. Save the token in ~/install_values.txt.
    2. Follow the instructions here to configure your endpoint. Save the URL in ~/install_values.txt.
  2. In your CLI, login to the OpenShift cluster where you plan to install RHTAP.
  3. Make sure you are in the rhtap-cli directory.

    $ cd ~/rhtap-cli
  4. Run the integration command. Replace $ENDPOINT with your ACS central endpoint URL, and $TOKEN with your ACS API token.

    ./bin/rhtap-cli integration acs --endpoint="$ENDPOINT" --token="$TOKEN"

3.2. Integrating Quay

In this procedure, you obtain two values from your instance of Quay. Then you integrate your instance into RHTAP.

Prerequisites:

  • A Quay account
  • Ownership of a Quay organization (you can use any plan, including the free option).
Note

We recommend using a robot account in Quay for this procedure. This way, once RHTAP is installed, multiple users can authenticate to your organization’s namespace in Quay.

Procedure:

  1. In your web browser, login to Quay. On the right side of the banner, select your username and select Account Settings from the dropdown menu.
  2. On your user settings page, under Docker CLI Password, select Generate Encrypted Password. In the popup window, enter your password to authenticate.
  3. Next, still in the popup window, select Docker Configuration > View [username]-auth.json. Copy the string, without the quotation marks, following "auth":.
  4. In your ~/install_values.txt file, label and create the Docker configuration value with the following format, using your username and auth token where appropriate: {"auths": {"quay.io": {"auth": "[auth token]","email": ""}}}
  5. Back in the Quay UI, return to the default Repositories page. On the right side, under Users and Organizations, select the Quay organization you want to use for RHTAP.
  6. From the tabs on the left side, select Applications.
  7. Click Create New Application. Give your application a name.
  8. Click on the application’s name.
  9. From the tabs on the left, select Generate Token.
  10. From the options for permissions for the token, select View all visible repositories.
  11. Click Generate Access Token.
  12. Click Authorize Applicaiton.
  13. The UI displays an access token. Label and save this token in ~/install_values.txt, too.
  14. In your CLI, make sure you are in the rhtap-cli directory.

    $ cd ~/rhtap-cli
  15. Run the following command to integrate your instance of Quay. Replace $DOCKERCONFIGJSON with the Docker configuration value. Replace $API_TOKEN with the token you just generated. And replace $URL with the address for your instance of Quay (https://quay.io if you have not installed Quay in your cluster).

    $ ./bin/rhtap-cli integration quay --dockerconfigjson="$DOCKERCONFIGJSON" --token="$API_TOKEN" --url="$URL"

3.3. (Optional) Integrating Jenkins

Prerequisites

  • You must have the necessary permissions to create and manage Jenkins jobs.
  • You must have a URL using which you access Jenkins, a Jenkins user ID, and an API token.

Procedure

  1. In your CLI, make sure you are in the rhtap-cli directory.

    $ cd ~/rhtap-cli
  2. Run the integration command. Replace $API_TOKEN with your Jenkins API token, $URL with you Jenkins instance URL, $USERNAME with your Jenkins user ID.

    $ ./bin/rhtap-cli integration jenkins --token="$API_TOKEN" --url="$URL" --username="$USERNAME"

3.4. (Optional) Integrating GitLab

Prerequisites

  • You must have the necessary permissions to create and manage GitLab jobs.
  • You must have a GitLab API token.
  • You must have a host URL, if you plan to integrate with a custom GitLab host. If you do not specify a GitLab host URL, the system defaults to gitlab.com.

Procedure

  1. In your CLI, make sure you are in the rhtap-cli directory.

    $ cd ~/rhtap-cli
  2. Run the integration command. Replace $API_TOKEN with your GitLab API token. If you are integrating with a custom GitLab host, replace $HOST_URL with you GitLab host URL. If you are using the default gitlab.com host, you can remove the --host option.

    $ ./bin/rhtap-cli integration gitlab --token="$API_TOKEN" --host="$HOST_URL"
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red Hat
Back to top