ansible · jklech-work · Apr 28, 2026
diff --git a/downstream/assemblies/platform/assembly-inventory-introduction.adoc b/downstream/assemblies/platform/assembly-inventory-introduction.adoc
@@ -16,20 +16,14 @@ Inventory files listed in this document are shown in `ini` format.
 The location of the inventory file depends on the installation program you used.
 The following table shows possible locations:
 
-[NOTE]
-====
-The {PlatformNameShort} RPM installer was deprecated in 2.5 and will be removed in {PlatformNameShort} 2.7. The RPM installer will be supported for RHEL 9 during the lifecycle of {PlatformNameShort} 2.6 to support migrations to existing supported topologies.
-For more information on upgrade and migration paths, see the link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/{PlatformVers}/html-single/planning_your_upgrade/index#upgrade-support-matrix[Support matrix for upgrade scenarios].
-====
-
 [cols="30%,70%",options="header"]
 |====
 | Installer | Location
-| *RPM* | `/opt/ansible-automation-platform/installer`
-| *RPM bundle tar* | `/ansible-automation-platform-setup-bundle-<latest-version>`
-| *RPM non-bundle tar* | `/ansible-automation-platform-setup-<latest-version>`
 | *Container bundle tar* | `/ansible-automation-platform-containerized-setup-bundle-<latest-version>`
 | *Container non-bundle tar* | `/ansible-automation-platform-containerized-setup-<latest-version>`
+| *RPM (deprecated)* | `/opt/ansible-automation-platform/installer`
+| *RPM bundle tar (deprecated)* | `/ansible-automation-platform-setup-bundle-<latest-version>`
+| *RPM non-bundle tar (deprecated)* | `/ansible-automation-platform-setup-<latest-version>`
 |====
 
 You can verify the hosts in your inventory by using the command:
@@ -82,7 +76,7 @@ automationgateway_pg_password=""
 
 The first part of the inventory file specifies the hosts or groups that Ansible can work with.
 
-For more information on `registry_username` and `registry_password`, see link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/containerized_installation/preparing-containerized-installation#proc-set-registry-username-password[Setting registry_username and registry_password].
+For more information on `registry_username` and `registry_password`, see link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/html/containerized_installation/preparing-containerized-installation#proc-set-registry-username-password[Setting registry_username and registry_password].
 
 include::snippets/snip-gateway-component-description.adoc[leveloffset=+1]
 

diff --git a/downstream/assemblies/platform/assembly-system-requirements.adoc b/downstream/assemblies/platform/assembly-system-requirements.adoc
@@ -16,11 +16,11 @@ Use this information when planning your {PlatformName} installations and designi
 * Configured an NTP client on all nodes.
 
 ifdef::aap-plan[]
-include::platform/ref-RPM-system-requirements.adoc[leveloffset=+1]
-
 include::platform/ref-containerized-system-requirements.adoc[leveloffset=+1]
 
 include::platform/ref-OCP-system-requirements.adoc[leveloffset=+1]
+
+include::platform/ref-RPM-system-requirements.adoc[leveloffset=+1]
 endif::aap-plan[]
 
 ifdef::aap-install[]

diff --git a/downstream/modules/platform/con-editing-inventory-files.adoc b/downstream/modules/platform/con-editing-inventory-files.adoc
@@ -10,4 +10,4 @@ These configurations add optional features for managing your {PlatformName} depl
 
 Add these variables by editing the inventory file with a text editor.
 
-A table of predefined values for inventory file variables can be found in link:{BaseURL}/red_hat_ansible_automation_platform/{PlatformVers}/html/rpm_installation/appendix-inventory-files-vars[Inventory file variables] in the _{PlatformName} Installation Guide_.
+A table of predefined values for inventory file variables can be found in link:{BaseURL}/red_hat_ansible_automation_platform/2.7/html/containerized_installation/appendix-inventory-files-vars[Inventory file variables] in the _Containerized installation guide_.
diff --git a/downstream/modules/platform/con-gw-clustered-redis.adoc b/downstream/modules/platform/con-gw-clustered-redis.adoc
@@ -12,9 +12,9 @@ Clustered Redis, shared between the {Gateway} and {EDAName}, is the default conf
 
 [NOTE]
 ====
-A Redis high availability (HA) compatible deployment require 6 VMs. 
-In RPM deployments, Redis can be colocated on each {PlatformNameShort} component VM except for {ControllerName}, execution nodes, or the PostgreSQL database.
+A Redis high availability (HA) compatible deployment require 6 VMs.
 In containerized deployments, Redis can be colocated on any {PlatformNameShort} component VMs of your choice except for execution nodes or the PostgreSQL database.
+In legacy RPM deployments (deprecated), Redis can be colocated on each {PlatformNameShort} component VM except for {ControllerName}, execution nodes, or the PostgreSQL database.
 See {LinkTopologies} for the opinionated deployment options available. 
 ====
 

diff --git a/downstream/modules/platform/proc-installing-with-internet.adoc b/downstream/modules/platform/proc-installing-with-internet.adoc
@@ -33,21 +33,16 @@ $ tar xvzf aap-bundled-installer.tar.gz
 -----
 ====
 
-. To install the RPM, install {PlatformNameShort} Installer Package:
+. *RPM installation (deprecated):* To install by using the RPM method, install the {PlatformNameShort} Installer Package. RPM-based installation is removed in {PlatformNameShort} 2.7. For new installations, use the tarball method in step 1.
 +
-v.{PlatformVers} for RHEL 9 for x86_64
+v.2.6 for RHEL 9 for x86_64
 +
 ----
 $ sudo dnf install --enablerepo=ansible-automation-platform-2.6-for-rhel-9-x86_64-rpms ansible-automation-platform-installer
 ----
 +
 [NOTE]
 ====
-The {PlatformNameShort} RPM installer was deprecated in 2.5 and will be removed in {PlatformNameShort} 2.7. The RPM installer will be supported for RHEL 9 during the lifecycle of {PlatformNameShort} 2.6 to support migrations to existing supported topologies. For more information on upgrade and migration paths, see the link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/{PlatformVers}/html-single/planning_your_upgrade/index#upgrade-support-matrix[Support matrix for upgrade scenarios].
-====
-+
-[NOTE]
-====
 `dnf install` enables the repository as the repository is disabled by default.
 ====
 +

diff --git a/downstream/modules/platform/ref-RPM-system-requirements.adoc b/downstream/modules/platform/ref-RPM-system-requirements.adoc
@@ -2,14 +2,11 @@
 
 [id="ref-RPM-system-requirements_{context}"]
 
-= System requirements for RPM installation
+= System requirements for RPM installation (deprecated)
 
 [role="_abstract"]
-Review system requirements to ensure your environment supports RPM installation of {PlatformNameShort}. RPM-based installations of {PlatformNameShort} were deprecated in 2.5 and will be removed in version 2.7.
+RPM-based installation is removed in {PlatformNameShort} 2.7. For new installations, use the containerized installer or the {OCPShort} operator. The following information is provided for reference only.
 
 For system requirements for the RPM installation method of {PlatformNameShort}, see the link:{URLInstallationGuide}/platform-system-requirements[System requirements] section of _{TitleInstallationGuide}_.
 
-[NOTE]
-====
-The {PlatformNameShort} RPM installer was deprecated in 2.5 and will be removed in {PlatformNameShort} 2.7. The RPM installer will be supported for RHEL 9 during the lifecycle of {PlatformNameShort} 2.6 to support migrations to existing supported topologies. For more information on upgrade and migration paths, see the link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/{PlatformVers}/html-single/planning_your_upgrade/index#upgrade-support-matrix[Support matrix for upgrade scenarios].
-====
+For more information on upgrade and migration paths from RPM-based installations, see the link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/html-single/planning_your_upgrade/index#upgrade-support-matrix[Support matrix for upgrade scenarios].
diff --git a/downstream/modules/platform/ref-guidelines-hosts-groups.adoc b/downstream/modules/platform/ref-guidelines-hosts-groups.adoc
@@ -49,8 +49,8 @@ If you use one value in `[database]` and both {ControllerName} and {HubNameMain}
 
 *{EDAName}*
 
-* For RPM installations: {EDAName} must be installed on a separate server and cannot be installed on the same host as {HubName} and {ControllerName}.
-* For containerized installations: {EDAName} is co-located with all other {PlatformNameShort} components in the growth topolgy. In the enterprise topology, {EDAName} runs on separate dedicated nodes. 
+* For containerized installations: {EDAName} is co-located with all other {PlatformNameShort} components in the growth topology. In the enterprise topology, {EDAName} runs on separate dedicated nodes.
+* For legacy RPM installations (deprecated): {EDAName} must be installed on a separate server and cannot be installed on the same host as {HubName} and {ControllerName}.
 
 *{GatewayStart}*
 

diff --git a/downstream/modules/platform/ref-network-ports-protocols-diagram.adoc b/downstream/modules/platform/ref-network-ports-protocols-diagram.adoc
@@ -14,36 +14,29 @@ Hop nodes are an option for connecting control and execution nodes.
 Hop nodes use minimal CPU and memory, so vertically scaling hop nodes does not impact system capacity.
 ====
 
-*RPM based installations*
-
-[NOTE]
-====
-The following diagram shows client initiated connections between {PlatformNameShort} components.
-Direct connections shown in the diagram between the Client and {HubName}, {EDAName}, and {ControllerName} only apply when systems are upgraded from {PlatformName} 2.4 to {PlatformName} {PlatformVers}.
-This provides backward compatibility.
-====
-
-**{PlatformNameShort} Client initiated network ports and protocols**
-
-image::network_client_initiated.png[Interaction of {PlatformNameShort} components on the network with information about the ports and protocols that are used.]
+*Container-based installations*
 
 [NOTE]
 ====
-The following diagram shows internally initiated connections between {PlatformNameShort} components for new installs {PlatformName} {PlatformVers}.
+The following diagram shows connections between {PlatformNameShort} components. All external client traffic is routed through {Gateway}. Direct external access to {HubName}, {EDAName}, and {ControllerName} is not available.
 ====
 
-**{PlatformNameShort} Internally initiated network ports and protocols**
+**{PlatformNameShort} network ports and protocols**
 
-image::network_internally_initiated.png[Interaction of {PlatformNameShort} components on the network with information about the ports and protocols that are used.]
+image::Container-network_internally_initiated.png[Interaction of {PlatformNameShort} components on the network with information about the ports and protocols that are used in a container-based installation.]
 
 
-*Container-based installations*
+*RPM-based installations (deprecated)*
 
 [NOTE]
 ====
-The following diagram shows connections between {PlatformNameShort} components for a container-based installation {PlatformName} {PlatformVers}.
+The following diagrams applied to RPM-based installations in {PlatformNameShort} 2.6 and earlier. RPM-based installation is removed in {PlatformNameShort} 2.7. In {PlatformNameShort} 2.7, all external client traffic is routed through {Gateway}. Direct external access to {HubName}, {EDAName}, and {ControllerName} is no longer available.
 ====
 
-**Containerized {PlatformNameShort} network ports and protocols**
+**{PlatformNameShort} Client initiated network ports and protocols (deprecated)**
+
+image::network_client_initiated.png[Interaction of {PlatformNameShort} components on the network with information about the ports and protocols that are used.]
+
+**{PlatformNameShort} Internally initiated network ports and protocols (deprecated)**
 
-image::Container-network_internally_initiated.png[Interaction of {PlatformNameShort} components on the network with information about the ports and protocols that are used in a container-based installation.]
+image::network_internally_initiated.png[Interaction of {PlatformNameShort} components on the network with information about the ports and protocols that are used.]
Original file line number	Diff line number	Diff line change
Expand Up		@@ -10,4 +10,4 @@ These configurations add optional features for managing your {PlatformName} depl

		Add these variables by editing the inventory file with a text editor.

		A table of predefined values for inventory file variables can be found in link:{BaseURL}/red_hat_ansible_automation_platform/{PlatformVers}/html/rpm_installation/appendix-inventory-files-vars[Inventory file variables] in the _{PlatformName} Installation Guide_.
		A table of predefined values for inventory file variables can be found in link:{BaseURL}/red_hat_ansible_automation_platform/2.7/html/containerized_installation/appendix-inventory-files-vars[Inventory file variables] in the _Containerized installation guide_.