Install the Ansible automation portal Helm chart

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

Configure the Helm chart from the OpenShift catalog

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

Before you begin

You have created a project for Ansible automation portal in OpenShift Container Platform.
You have created secrets in OpenShift Container Platform for Red Hat 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.
- For HTTP plug-in registry (deprecated): You have deployed the plug-in registry and plan to set pluginMode to tarball.
Helm charts are enabled in the OpenShift Container Platform developer catalog. If the Automation Portal chart does not appear in the catalog, verify that the HelmChartRepository custom resources are not disabled. For more information, see Working with Helm charts in the OpenShift Container Platform documentation.

Procedure

In the OpenShift Container Platform web console, select the Developer perspective.
Select your project and click the Helm option in the OpenShift sidebar.
Click Create and select Helm Release.
Search for Portal in the Helm Charts filter, and select the Automation Portal chart.
Click Create and select the YAML view.
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
```
Configure the plug-in delivery mode and version by setting the pluginMode and imageTagInfo keys:
- For OCI delivery, set pluginMode to oci.
Set imageTagInfo to the plug-in version from the Helm chart or the lifecycle page. To determine the correct version tag, see "Determine version tags before you install".
```
redhat-developer-hub:
  global:
    pluginMode: oci
    imageTagInfo: "<plugin-version>"
```

Set the Red Hat 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>"

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

Click Create.

Verify the installation

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

Procedure

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

The deployment appears with the label D on the icon. 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.

Figure 1. OpenShift deployment topology view