When Red Hat Ansible Automation Platform is central to your enterprise environment, a controller outage halts continuous integration and continuous delivery (CI/CD) pipelines and automated remediation. To maintain continuous availability and prevent downtime, platform teams can use a federated multi-cluster deployment managed through GitOps. This approach uses Git repositories as a single source of truth to declaratively manage, automate, and audit Infrastructure as Code (IaC).
End-to-end enterprise architecture
Decoupling platform configuration from workload execution allows GitHub Actions to coordinate deployment while integrating directly with ServiceNow for change governance and Splunk for central logging.
Figure 1 illustrates the end-to-end architecture connecting change governance, GitOps automation, multi-cluster execution, and centralized logging.
This GitOps framework coordinates platform configuration and application delivery across two operational stages.
Declarative infrastructure provisioning (main branch)
Pushing platform updates to the main
branch automatically triggers playbooks/configure_aap.yml
. The workflow runs inside the quay.io/jopaik/aap-runner:jp1
execution environment, which contains a supported execution environment with Red Hat Ansible Certified Content Collections). It iterates across all gateways (AAP-Platform-DC1
and AAP-Platform-DC2
) using ansible.controller modules to establish core automation settings.
During execution, the playbook…