Chapter 4. Upgrading the Ansible plug-ins on a Helm installation on OpenShift Container Platform

Procedure

1. Log in to your OpenShift Container Platform instance.
2. In the OpenShift Developer UI, navigate to Helm developer-hub Actions Upgrade Yaml view.

3. In the global.dynamic.plugins list, update the version tag at the end of each package URL:

   plugins:
     - disabled: false
       package: 'oci://registry.redhat.io/ansible-automation-platform/automation-portal:2.1!ansible-plugin-backstage-rhaap'
       pluginConfig:
         ...
     - disabled: false
       package: 'oci://registry.redhat.io/ansible-automation-platform/automation-portal:2.1!ansible-plugin-scaffolder-backend-module-backstage-rhaap'
       pluginConfig:
         ...

4. Click Upgrade.

   The Red Hat Developer Hub pods restart and pull the new plug-in version.

Verification

1. In the OpenShift UI, click Topology.
2. Verify that the Red Hat Developer Hub instance is available.

Procedure

1. In a browser, navigate to the Red Hat Ansible Automation Platform Product Software downloads page and select the Product Software tab.

2. Click Download now next to Ansible plug-ins for Red Hat Developer Hub Setup Bundle to download the latest version of the plug-ins.

   The format of the filename is ansible-rhdh-plugins-x.y.z.tar.gz. Substitute the Ansible plug-ins release version, for example 2.0.0, for x.y.z.

3. Create a directory on your local machine to store the .tar files.

   $ mkdir /path/to/<ansible-backstage-plugins-local-dir-changeme>

4. Set an environment variable ($DYNAMIC_PLUGIN_ROOT_DIR) to represent the directory path.

   $ export DYNAMIC_PLUGIN_ROOT_DIR=/path/to/<ansible-backstage-plugins-local-dir-changeme>

5. Extract the ansible-rhdh-plugins-<version-number>.tar.gz contents to $DYNAMIC_PLUGIN_ROOT_DIR.

   $ tar --exclude='*code*' -xzf ansible-rhdh-plugins-x.y.z.tar.gz -C $DYNAMIC_PLUGIN_ROOT_DIR

   Substitute the Ansible plug-ins release version, for example 2.0.0, for x.y.z.

Procedure

1. Log in to your OpenShift Container Platform instance with credentials to create a new application.

2. Open your Red Hat Developer Hub OpenShift project.

   $ oc project <YOUR_DEVELOPER_HUB_PROJECT>

3. Run the following commands to update your plug-in registry build in the OpenShift cluster. The commands assume that $DYNAMIC_PLUGIN_ROOT_DIR represents the directory for your .tar files. Replace this in the command if you have chosen a different environment variable name.

   $ oc start-build plugin-registry --from-dir=$DYNAMIC_PLUGIN_ROOT_DIR --wait

4. When the registry has started, the output displays the following message:

   Uploading directory "/path/to/dynamic_plugin_root" as binary input for the build …
   Uploading finished
   build.build.openshift.io/plugin-registry-1 started

1. In the OpenShift UI, click Topology.
2. Click the redhat-developer-hub icon to view the pods for the plug-in registry.
3. Click View logs for the plug-in registry pod.
4. Open the Terminal tab and run ls to view the .tar files in the plug-in registry.
5. Verify that the new .tar file has been uploaded.

Procedure

1. Log in to your OpenShift Container Platform instance.
2. In the OpenShift Developer UI, navigate to Helm developer-hub Actions Upgrade Yaml view.

3. Locate the global section.

   ...
   global:
     # Ensure OCI mode is enabled
     pluginMode: oci
   
     # UPDATE this value to the new desired version
     imageTagInfo: "2.1"
   
     # Note: Do not manually update 'plugins' packages;
     # OCI mode handles the download automatically based on the tag above.
     dynamic:
       plugins: []

4. Click Upgrade.

   The Red Hat Developer Hub pods restart and pull the new plug-in versions.

Verification

1. In the OpenShift UI, click Topology.
2. Make sure that the Red Hat Developer Hub instance is available.