Red Hat Summit Red Hat Summitサポートコンソール開発者トライアルの開始お問い合わせ

このコンテンツは選択した言語では利用できません。

Chapter 5. 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. Clear 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 tssc.
  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 installation program manages and installs all required operator subscriptions.
    • manageSubscription: false: The installation program skips installing required operator subscriptions. When set to false, Operators installed before deploying RHADS must have Update Approval set to Automatic. If it is set to Manual, the installation might fail with a timeout.
    • Ensure that existing operators are compatible with RHADS - SSC. Incompatible versions might cause installation failure.

5.1. Customizing the tssc.products section of the config.yaml file
リンクのコピー

Customize the tssc.products section to adjust the default products and features. 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.

Procedure

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

        - name: Developer Hub
      properties:
        catalogURL: https://github.com/redhat-appstudio/tssc-sample-templates/blob/release-v1.7.x/all.yaml
    Copy to Clipboard Toggle word wrap

  2. To disable automatic installation of components that are already integrated externally, set enabled: false: 

        - name: Advanced Cluster Security
      enabled: false
      namespace: tssc-acs
    Copy to Clipboard Toggle word wrap
    Note

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

  3. To select your Identity and Access Management (IAM) provider, set authProvider: 

        - name: Developer Hub
        authProvider: <github|gitlab>
    Copy to Clipboard Toggle word wrap

    You can specify github (default) or gitlab.

    Important

    You must integrate the authentication provider that you choose.

  4. To enable role-based access control (RBAC) for Developer Hub, set RBAC.enabled to true: 

        - name: Developer Hub
        authProvider: <github|gitlab>
        RBAC:
          enabled: true
        # adminUsers:
        #   - <username>
        # orgs:
        #   - <github_org>
    Copy to Clipboard Toggle word wrap
    Note

    If you do not define adminUsers, the installation program defaults to the GitHub or GitLab credentials specified during integration. If you specify GitHub as your IAM provider, you can specify an orgs list, but if you specify GitLab it will ignore the orgs list and default to the organization specified in the integration configuration.

  5. 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: 

          - name: Developer Hub
      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`
      Copy to Clipboard Toggle word wrap
  6. After you complete all necessary changes, you can push it to the cluster using the tssc config --create ` command. If you are updating a configuration that you have already pushed, specify the `--force option too. Once you push the configuration, you can run the tssc deploy command again to implement the changes.
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

Theme

© 2026 Red Hatトップに戻る