Red Hat Ansible Automation Platform 2.7 is now generally available. Whether you are planning a new deployment or upgrading from an existing installation, this guide covers what you need to know before you get started. We will include support installation methods, infrastructure requirements, and the upgrade paths available from version 2.6.
New installation of Ansible Automation Platform 2.7
Ansible Automation Platform 2.7 offers flexible installation methods to suit your infrastructure, with support for deployments on Red Hat Enterprise Linux (RHEL) and Red Hat OpenShift.
RHEL installation
For new installations on RHEL, the containerized installer is the only supported method in Ansible Automation Platform 2.7. It runs all platform components as Podman-based rootless containers on top of RHEL 9 (requires RHEL 9.6 or later versions) or RHEL 10, giving you a secure, manageable deployment without requiring root access during operation.
Two topology options are available for containerized deployments:
- Growth topology: A smaller footprint, all-in-one deployment without redundancy, suited for organizations getting started with Ansible Automation Platform. This requires a single VM with a minimum of 16 GB RAM. 4 CPUs, and a 60 GB disk.
- Enterprise topology: A multi-VM deployment with higher compute for larger volumes of automation, suitable for production use. This requires separate VMs for platform gateway, automation controller, automation hub, event-driven, and execution nodes, with an external database and HAProxy load balancer.
Both topologies use PostgreSQL 15 for installer-managed databases. External (customer-provided) databases must run PostgreSQL 15, 16, or 17 with ICU support enabled.
Read the containerized installation documentation.
In 2.7, we removed the RPM-based installer, deprecated since Ansible Automation Platform 2.6. It is no longer available for any version of RHEL. If you are currently running an RPM-based deployment, you must migrate to the containerized installer before your upgrade to 2.7. The following upgrade section will cover supported migration paths.
OpenShift Container Platform installation
For cloud-native and Kubernetes environments, the supported method is the operator-based installation on Red Hat OpenShift Container Platform. The Ansible Automation Platform operator is available on OpenShift Container Platform 4.14 through 4.22 and provides simplified maintenance, lifecycle management, and enterprise scalability through the platform gateway unified interface.
Two topology options are available for OpenShift deployments:
- Operator growth topology: A single-node OpenShift deployment for organizations getting started on OpenShift. This requires 32 GB RAM, 16 CPUs, and 128 GB local disk.
- Operator enterprise topology: A multi-node OpenShift cluster deployment for production workloads, using external Redis, PostgreSQL, and object storage for additional scalability and reliability.
Read the OpenShift installation documentation.
Upgrade to Ansible Automation Platform 2.7
Ansible Automation Platform 2.7 supports upgrading from the latest version of 2.6 to containerized and OpenShift Container Platform deployments. If you are running an earlier version or an RPM-based deployment, you must first reach a supported 2.6 deployment before upgrading to 2.7.
Upgrade vs. migration
An upgrade changes the Ansible Automation Platform software version (for example, from 2.6 to 2.7) while keeping the same installation type and RHEL version. A migration involves changing the installation type of the underlying RHEL major version and requires a backup and restore procedure.
Container-based upgrade scenarios
The following tables show the supported upgrade and migration paths from Ansible Automation Platform 2.6 containerized deployments to 2.7.
From container-based Ansible Automation Platform 2.6 on RHEL 9:
| Source | Target | Process |
|---|---|---|
| Container 2.6 on RHEL 9 | Container 2.7 on RHEL 9 | Upgrade - direct in-place upgrade from 2.6 to 2.7 |
| Container 2.6 on RHEL 9 | Container 2.7 on RHEL 10 | Migrate - upgrade to 2.7 on RHEL 9, then backup and restore to a fresh RHEL 10 installation running 2.7 |
| Container 2.6 on RHEL 9 | 2.7 on OpenShift Container Platform | Migrate - upgrade to container 2.7 on RHEL 9, then migrate to OpenShift Container Platform |
From container-based Ansible Automation Platform 2.6 on RHEL 10:
| Source | Target | Process |
|---|---|---|
| Container 2.6 on RHEL 10 | Container 2.7 on RHEL 10 | Upgrade - direct in-place upgrade from 2.6 to 2.7 |
| Container 2.6 on RHEL 10 | 2.7 on OpenShift Container Platform | Migrate - upgrade to container 2.7 on RHEL 10, then migrate to OpenShift Container Platform |
OpenShift Container Platform upgrade scenarios
If your current Ansible Automation Platform 2.6 deployment runs on OpenShift Container Platform, a direct in-place upgrade to 2.7 is available by changing the operator subscription channel to stable-2.7 in the OpenShift console.
Before you upgrade
Before beginning an upgrade to Ansible Automation Platform 2.7, review the following checklist:
- Verify your current deployment is running Ansible Automation Platform 2.6.
- Review the Ansible Automation Platform 2.7 release notes for any changes that may affect your deployment.
- If you are on a RPM-based deployment, you must migrate to a containerized or OpenShift-based deployment before upgrading to 2.7. The RPM installer is no longer available in this release.
Refer to the upgrade instructions for more information.
Learn more
Upgrading to Ansible Automation Platform 2.7 delivers new tools for AI-driven automation, a streamlined developer experience, and expanded self-service capabilities. Moving to the latest version ensures your organization benefits from the latest security patches, platform improvements, and new features.
Learn more about Ansible Automation Platform 2.7:
- Documentation: Ansible Automation Platform 2.7
- Website: What's new in Ansible Automation Platform
- Blog: What's new in Ansible Automation Platform 2.7
- Website: Upgrade Ansible Automation Platform
