---
title: "Federated multi-cluster Ansible Automation Platform with GitOps"
description: "An outage of a central Red Hat Ansible Automation Platform controller halts CI/CD pipelines and automated remediation. To maintain continuous availability, platform teams can deploy a federated multi-cluster architecture managed through GitOps, using Git repositories as a single source of truth for declarative Infrastructure as Code. This approach decouples platform configuration from workload execution, with GitHub Actions coordinating deployment and integrating with ServiceNow for change governance and Splunk for centralized logging. The framework operates in two stages: declarative infrastructure provisioning via the main branch runs playbooks/configure_aap.yml to configure enterprise settings and inventory mappings, while dynamic workload dispatch via the deploy branch uses playbooks/dispatch_round_robin.yml to route jobs across clusters using round-robin or explicit targeting. Key use cases include continuous operations across geographic clusters, rolling updates by diverting workloads to a secondary datacenter, and phased platform migrations by running distinct Ansible Automation Platform versions side by side."
---

# Federated multi-cluster Ansible Automation Platform with GitOps

[Red Hat](https://yomu.fyi/company/red-hat) · Joon Paik · Oct 30, 2026

**Type:** Problem & solution

## Summary

An outage of a central Red Hat Ansible Automation Platform controller halts CI/CD pipelines and automated remediation. To maintain continuous availability, platform teams can deploy a federated multi-cluster architecture managed through GitOps, using Git repositories as a single source of truth for declarative Infrastructure as Code. This approach decouples platform configuration from workload execution, with GitHub Actions coordinating deployment and integrating with ServiceNow for change governance and Splunk for centralized logging. The framework operates in two stages: declarative infrastructure provisioning via the main branch runs playbooks/configure\_aap.yml to configure enterprise settings and inventory mappings, while dynamic workload dispatch via the deploy branch uses playbooks/dispatch\_round\_robin.yml to route jobs across clusters using round-robin or explicit targeting. Key use cases include continuous operations across geographic clusters, rolling updates by diverting workloads to a secondary datacenter, and phased platform migrations by running distinct Ansible Automation Platform versions side by side.

## Context

A central Red Hat Ansible Automation Platform controller outage halts CI/CD pipelines and automated remediation, requiring a federated multi-cluster approach for continuous availability.

## Approach / What changed

Federated multi-cluster deployment managed through GitOps, using Git repositories as single source of truth, with two operational stages: declarative infrastructure provisioning via main branch and dynamic workload dispatch via deploy branch, integrating with ServiceNow and Splunk.

## Takeaways

- The architecture decouples platform configuration from workload execution, allowing GitHub Actions to coordinate deployment while integrating with ServiceNow for change governance and Splunk for logging.
- The main branch triggers playbooks/configure\_aap.yml to configure enterprise settings, inventory mappings, and synchronize Git workload repositories, while the deploy branch uses playbooks/dispatch\_round\_robin.yml to route jobs across clusters using round-robin or explicit targeting.
- Key use cases include continuous operations across geographic clusters, rolling updates by diverting workloads to a secondary datacenter, and phased platform migrations by running distinct Ansible Automation Platform versions side by side.

## FAQ

### How does the GitOps framework handle workload routing across clusters?

The deploy branch playbook dispatch\_round\_robin.yml evaluates the target\_aap variable; if set to auto, jobs alternate across clusters using the GitHub index round-robin algorithm; if set to an explicit environment like dc1, it filters gateway labels accordingly.

### What enterprise integrations does this architecture support?

It integrates with ServiceNow Flow Designer to initiate deployment pipelines upon change request approval, and streams event logs to centralized analytics platforms such as Splunk.

### What are the primary use cases for federated multi-cluster Ansible Automation Platform?

Continuous operations across geographic clusters, rolling updates by diverting workloads to a secondary datacenter during maintenance, and phased platform migrations by running distinct Ansible Automation Platform versions side by side.

**Tags:** [Ansible](https://yomu.fyi/topic/ansible), [CI/CD](https://yomu.fyi/topic/ci-cd), [GitOps](https://yomu.fyi/topic/gitops), [High Availability](https://yomu.fyi/topic/high-availability), [Infrastructure](https://yomu.fyi/topic/infrastructure)

- Source: [Red Hat](https://developers.redhat.com/articles/2026/10/30/federated-multi-cluster-ansible-automation-platform-gitops)
- Source URL: https://developers.redhat.com/articles/2026/10/30/federated-multi-cluster-ansible-automation-platform-gitops
- Ingested by Yomu: 2026-10-30T15:00:10.179Z

[Read original post](https://developers.redhat.com/articles/2026/10/30/federated-multi-cluster-ansible-automation-platform-gitops)
