Chapter 3. Customizing the config.yaml file

Procedure

1. In the OpenShift console, switch to the Administrator perspective.
2. Go to Workloads > ConfigMaps.
3. From the Project drop down list, select RHTAP.
4. Open the rhtap-cli-config ConfigMap.

5. Select the YAML view and navigate to where config.yaml parameters are defined.

   Note

   • If your cluster already includes the required subscriptions or operators, you can prevent the installer from creating new ones by setting the manageSubscription property to false.

     • manageSubscription: true (default): The installer manages and installs all required operator subscriptions.

   • manageSubscription: false: The installer skips installing required operator subscriptions because it assumes they already exist on the cluster.

     • Ensure that the pre-installed operators are compatible with RHTAP. Incompatible versions or configurations may cause the installation to fail.

6. Update the following fields as needed:

   1. To use a custom software catalog, set the catalogURL:

      Copy to Clipboard Toggle word wrap

      redhatDeveloperHub:
        properties:
          catalogURL: https://github.com/<your-org>/tssc-sample-templates/blob/releases/all.yaml

   2. To disable installation of components you’ve integrated externally (for example, ACS and Quay):

      Copy to Clipboard Toggle word wrap

      redhatAdvancedClusterSecurity:
        enabled: &rhacsEnabled false
        namespace: &rhacsNamespace rhtap-rhacs
      
      redHatQuay:
        enabled: &quayEnabled false
        namespace: &quayNamespace rhtap-quay

      Note

      If you try to integrate outside products or pre-existing instances, but do not customize config.yaml, Red Hat Trusted Application Pipeline still installs and uses its default products. You must customize config.yaml for your rhtap-cli integration commands to take effect. However, if you do not customize config.yaml for your rhtap-cli integration, the installer deploys the product and overrides the existing integrations.

1. To enable the RBAC plugin in Developer Hub, configure the RBAC property in the redhatDeveloperHub section.

   Copy to Clipboard Toggle word wrap

     RBAC:
       enabled: true # Enables the RBAC feature.
       adminUsers: # GitHub usernames that should have administrator access.
         - yourGitHubUsername
         - anotherGitHubAdmin
       orgs: # GitHub organizations whose members are imported into the Developer Hub catalog with access roles.
         - your-github-org

   Note

   If you omit adminUsers or orgs, the installer defaults to the GitHub user and organization that were configured when integrating the GitHub application.

1. To use a custom namespace instead of the default one, configure the namespacePrefixes property in the redhatDeveloperHub section of the config.yaml file. By default, RHTAP creates four namespaces during installation:

   • rhtap-app-ci: For CI pipeline workloads

   • rhtap-app-development, rhtap-app-stage, and rhtap-app-prod: For development, staging, and prod deployments

     You can customize the prefixes for these namespaces and define additional namespace sets by using the namespacePrefixes property. For example, you can configure custom prefixes to generate namespaces such as my_prefix1-app-ci, my_prefix1-app-development, my_prefix1-app-stage, and my_prefix1-app-prod.

     Copy to Clipboard Toggle word wrap

     redhatDeveloperHub:
       namespacePrefixes:
         - my_prefix1
         - my_prefix2

     1. After you complete all necessary changes, select Save.