Upgrade the Ansible Automation Platform Operator

To upgrade to the latest version of Ansible Automation Platform Operator on OpenShift Container Platform, you can use the following procedure:

Before you begin

Important:

If you are upgrading from Ansible Automation Platform 2.4, your deployment does not include a platform gateway. After the operator upgrade completes, you must create an AnsibleAutomationPlatform custom resource (CR) and link it to your existing automation controller and automation hub instances. Without this step, your components remain isolated and the unified platform UI is not available.

Review  Plan your upgrade to Ansible Automation Platform 2.6for important changes to infrastructure, authentication, and identity access management that affect your upgrade from version 2.4.

  1. For existing deployments only: You must deploy your automation controller and automation hub instances to the same, single namespace before upgrading. For more information see, Migrating from one namespace to another.
  2. Review the Backup and restore in an OpenShift environment section and backup your services:
    • AutomationControllerBackup
    • AutomationHubBackup
    • EDABackup
Important:

Upgrading from Event-Driven Ansible 2.4 is not supported. If you are using Event-Driven Ansible 2.4 in production, contact Red Hat before you upgrade.

Procedure

  1. Log in to OpenShift Container Platform.
  2. Navigate to Operators > Installed Operators.
  3. Select the Ansible Automation Platform Operator installed on your project namespace.
  4. Select the Subscriptions tab.
  5. To upgrade to 2.6 change the channel to stable-2.6.
  6. Click Preview InstallPlan to review the InstallPlan.
  7. Click Approve.
  8. Ensure an AnsibleAutomationPlatform custom resource (CR) is deployed in your namespace.
    • Upgrading from version 2.4: Your deployment does not include a platform gateway. You must create an AnsibleAutomationPlatform CR and link it to your existing components. Follow the steps in Add components to an existing deployment, setting the controller.name and hub.name fields to the names of your existing instances.
    • Upgrading from version 2.5: Your deployment already includes the platform gateway. Verify that your existing CR is healthy after the upgrade.

    Run the following command to verify the CR exists:

    oc get ansibleautomationplatform -n <your-aap-namespace>
    Note:

    The automation controller and automation hub UIs remain until all SSO configuration is supported in the platform gateway UI.

Results

You can confirm you have upgraded successfully by navigating to Operators > Installed Operators, here under Ansible Automation Platform you can verify the version number matches your target version.

Additionally, go to your Ansible Automation Platform Operator deployment and click All instances to verify if all instances upgraded correctly. All pods should display either a Running or Completed status, with no pods displaying an error status.