2.4 multi node automation controller deployment to a 2.6 enterprise topology

Upgrade your 2.4 multi-node automation controller setup to a 2.6 enterprise topology. Review the required infrastructure changes and requirements needed to successfully plan the upgrade.

2.4 infrastructure topology diagram
Copy link

This diagram outlines the 2.4 infrastructure topology for this deployment model.

Figure 1. 2.4 infrastructure topology diagram

2.4 multi controller topology

2.6 infrastructure topology diagram
Copy link

This diagram outlines the 2.6 infrastructure topology that Red Hat has tested with this deployment model.

Figure 2. 2.6 infrastructure topology diagram

2.6 enterprise topology

Requirements for upgrading a multi node automation controller deployment on OpenShift Container Platform
Copy link

The following table highlights the requirements for upgrading from Ansible Automation Platform 2.4 to 2.6.

Expand
Existing 2.4 topology Tested 2.6 topology Requirements for each pod

Redundant automation controller-only deployment:

  • One automation controller web pod
  • One automation controller task pod
  • Two automation mesh ingress pods
  • Externally managed database service

Enterprise topology:

  • One automation controller web pod
  • One automation controller task pod
  • One automation hub web pod
  • One automation hub API pod
  • Two automation hub content pods
  • Two automation hub worker pods
  • One automation hub Redis pod
  • One Event-Driven Ansible controller API pod
  • Two Event-Driven Ansible controller activation worker pods
  • Two Event-Driven Ansible controller default worker pods
  • Two Event-Driven Ansible controller event stream pods
  • One Event-Driven Ansible controller scheduler pod
  • One platform gateway pod
  • Two automation mesh ingress pods
  • Externally managed database service
  • Externally managed Redis
  • Externally managed object storage service (for automation hub)

See the Operator enterprise topology section of Tested deployment models.