2.4 single automation controller and automation hub deployment to a 2.6 growth topology

Upgrade your 2.4 single-node deployment (automation controller and automation hub) to a 2.6 growth topology. Review the infrastructure changes and requirements needed to successfully plan your 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 single controller and hub 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 growth topology

Requirements for upgrading a single automation controller and automation hub deployment
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

Non-redundant automation controller and automation hub deployment:

  • 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 database pod

Growth 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
  • One Event-Driven Ansible controller activation worker pod
  • One Event-Driven Ansible controller default worker pod
  • One Event-Driven Ansible controller event stream pod
  • One Event-Driven Ansible controller scheduler pod
  • One platform gateway pod
  • One database pod
  • One Redis pod

See the Operator growth topology section of Tested deployment models.