Chapter 4. Install the self-service automation portal Helm chart


You can use the configured secrets and plugin registry to install the self-service automation portal. Deploy the application onto your OpenShift cluster using the provided Helm chart.

Deploy the Helm chart from the OpenShift catalog by configuring the base URL and organization name in the YAML view. This launches the self-service automation portal installation.

Prerequisites

  • You have created a project for self-service automation portal in OpenShift Container Platform.
  • You have created secrets in OpenShift Container Platform for Ansible Automation Platform authentication.
  • If you configure SCM integration (for example, importing from private repositories or using templates that access SCM), you have created secrets in OpenShift for SCM authentication.
  • You have completed one of the plug-in delivery methods:

    • For OCI delivery: You have created the <release-name>-dynamic-plugins-registry-auth secret.

Procedure

  1. In the OpenShift Container Platform web console, select the Developer view.
  2. Select your project and click the Helm option in the OpenShift sidebar.
  3. Click Create and select Helm Release.
  4. Search for Portal in the Helm Charts filter, and select the Automation Portal chart.
  5. Click Create and select the YAML view.
  6. Update the clusterRouterBase value with the base URL of your OpenShift instance.

    Important

    You must replace the default apps.example.com placeholder value. If the default value remains, Helm chart validation fails.

    redhat-developer-hub:
      global:
        clusterRouterBase: apps.example.com
  7. Configure the plug-in delivery mode by setting the pluginMode key:

    • For OCI delivery, set the value to oci.

      redhat-developer-hub:
        global:
          pluginMode: oci
  8. Optional: To use a specific plug-in version, update the imageTagInfo value:

    redhat-developer-hub:
      global:
        imageTagInfo: "2.1"
  9. Set the Ansible Automation Platform organization to synchronize. The default value is Default. Update the orgs key to match your organization name:

    redhat-developer-hub:
      upstream:
        backstage:
          appConfig:
            catalog:
              providers:
                rhaap:
                  '{{- include "catalog.providers.env" . }}':
                    orgs: "<your-aap-organization-name>"
  10. Optional: Update the CUSTOMER_SUPPORT_URL to point to your support portal:

    redhat-developer-hub:
      upstream:
        backstage:
          extraEnvVars:
            - name: CUSTOMER_SUPPORT_URL
              value: https://access.redhat.com/support
  11. Click Create.

Additional resources

4.2. Verify the installation

Verify the Helm chart installation from the OpenShift Container Platform web console.

Procedure

  1. In a browser, log in to your OpenShift instance.
  2. In the Developer view, navigate to the Topology view for the namespace where you deployed the Helm chart.

    The deployment appears: the label on the icon is D. The name of the deployment is <installation-name>-backstage, for example <my-self-service-automation-portal-backstage>.

    While it is deploying, the icon is light blue. The color changes to dark blue when deployment is complete.

    Deployment on OpenShift console
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