Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 3. Customizing the config.yaml file

Customize the config.yaml file before integrating external products and services to preserve your integration settings during installation.

Prerequisites

  • You have access to the OpenShift Web Console.
  • You plan to integrate at least one external product or service (For example, RHACS or Quay).

  • (Optional) Forked software catalog repository URL. RHADS - SSC provides a catalog of software templates that help developers scaffold applications. To customize these templates, fork the repository before installation.

    1. In your browser, go to the RHADS - SSC software catalog repository.

    2. Click Fork to fork the repository.

      1. Uncheck the box labeled Copy the main branch only.
    3. When the fork is created, copy its URL and save it in the private.env file.
    4. In the forked repository, click main to open the branch/tag dropdown.

    5. Under Tags, select the release that matches your RHADS - SSC version.

      Note

      Update your fork periodically to include changes from the upstream repository.

Procedure

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

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

    Note

    • To avoid reinstalling operator subscriptions already present on your cluster, set manageSubscription: false.

      • manageSubscription: true (default): The installer manages and installs all required operator subscriptions.
      • manageSubscription: false: The installer skips installing required operator subscriptions.
      • Ensure that existing operators are compatible with RHADS - SSC. Incompatible versions may cause installation failure.

Structure of the config.yaml file

The config.yaml file is structured under the main tssc object with these key attributes:

  • namespace: Defines the default installation namespace (typically tssc), serving as the primary operational area.
  • settings: Controls global deployment settings and properties.
  • products: Lists products and features for deployment, each identified by a unique name with associated properties.
  • dependencies: Specifies dependencies that the installer deploys in the order defined in the configuration file.

Customizing the tssc.products section

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

    developerHub:
  properties:
    catalogURL: https://github.com/<your-org>/tssc-sample-templates/blob/release-v1.6.x/all.yaml

  2. To disable automatic installation of components that are already integrated externally: 

    advancedClusterSecurity:
  enabled: &rhacsEnabled false
  namespace: &rhacsNamespace tssc-acs

quay:
  enabled: &quayEnabled false
  namespace: &quayNamespace tssc-quay
    Note

    If external integrations are not correctly reflected in the config.yaml, the installer will deploy default components. Update the file to prevent unintended provisioning.

  3. To enable role-based access control (RBAC) for Developer Hub: 

    developerHub:
  RBAC:
    enabled: true
    adminUsers:
      - yourGitHubUsername
      - anotherGitHubAdmin
    orgs:
      - your-github-org
    Note

    If you do not define adminUsers or orgs, the installer defaults to the GitHub credentials specified during integration.

  4. To use custom namespace prefixes instead of the default ones, configure the namespacePrefixes property. By default, RHADS - SSC creates the following namespaces during installation:

    • tssc-app-ci: For continuous integration pipeline workloads

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

      You can customize the prefixes for these namespaces and define additional sets. For example: 

    developerHub:
  namespacePrefixes:
    - my_prefix1  # This generates the following namespaces: `my_prefix1-app-ci`, `my_prefix1-app-development`, `my_prefix1-app-stage`, `my_prefix1-app-prod`
    - my_prefix2 # This generates the following namespaces: `my_prefix2-app-ci`, `my_prefix2-app-development`, `my_prefix2-app-stage`, `my_prefix2-app-prod`
  5. After you complete all necessary changes, select Save.
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 HatBack to top