--- title: Federated multi-cluster Ansible Automation Platform with... description: A GitOps pattern lets platform teams run Red Hat Ansible Automation Platform across multiple clusters without a single point of failure. Git becomes the source... canonical: https://daily.dev/posts/federated-multi-cluster-ansible-automation-platform-with-gitops-hoyxx8x0g twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Federated multi-cluster Ansible Automation Platform with GitOps | daily.dev og:description: A GitOps pattern lets platform teams run Red Hat Ansible Automation Platform across multiple clusters without a single point of failure. Git becomes the source... og:url: https://daily.dev/posts/federated-multi-cluster-ansible-automation-platform-with-gitops-hoyxx8x0g og:image: https://api.daily.dev/og/posts/Hoyxx8X0g.png og:image:alt: Federated multi-cluster Ansible Automation Platform with GitOps og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Federated multi-cluster Ansible Automation Platform with GitOps **[Red Hat Developer](https://daily.dev/sources/rhdev)** · 3 min read · 0 upvotes · 0 comments ## Summary A GitOps pattern lets platform teams run Red Hat Ansible Automation Platform across multiple clusters without a single point of failure. Git becomes the source of truth: pushing to the main branch triggers playbooks/configure_aap.yml to configure gateways like AAP-Platform-DC1 and AAP-Platform-DC2, while the deploy branch runs dispatch_round_robin.yml to route jobs across clusters. Setting target_aap to auto spreads jobs evenly using a round-robin algorithm. The setup also integrates with ServiceNow for change approval and Splunk for centralized logging, and supports rolling maintenance and phased version migrations. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How can I run Red Hat Ansible Automation Platform across multiple clusters without downtime during maintenance? Use a federated multi-cluster deployment managed through GitOps, where Git repositories act as the single source of truth. Pushing to the main branch triggers a playbook (configure_aap.yml) that configures all gateways, such as AAP-Platform-DC1 and AAP-Platform-DC2, letting teams divert workloads to one datacenter while performing OS upgrades on nodes in another without service interruption. _Teams designing zero-downtime automation platforms can track GitOps patterns like this on daily.dev._ ### How does round-robin job dispatch work across multiple Ansible Automation Platform clusters? Setting the target_aap variable to 'auto' in deploy_job.yml makes job execution alternate evenly across cluster instances using a GitHub index round-robin algorithm. Setting target_aap to an explicit value like dc1 or production instead filters gateway labels to target that specific environment. In production, dedicated infrastructure such as an F5 load balancer typically handles the actual load balancing. _Engineers building multi-cluster automation routing can compare approaches like this on daily.dev._ ## Similar posts on daily.dev - [Proximity automation with Red Hat Ansible Automation Platform and Red Hat OpenShift Virtualization](https://daily.dev/posts/proximity-automation-with-red-hat-ansible-automation-platform-and-red-hat-openshift-virtualization-a5fdhgr5o) · Red Hat Developer · 0 upvotes · 0 comments - [DevOps isn’t enough: GitOps strategies for regulated multicloud deployments](https://daily.dev/posts/devops-isn-t-enough-gitops-strategies-for-regulated-multicloud-deployments-qabg3ggfw) · All Things Open · 3 upvotes · 0 comments - [Multi-Agent and Multi-Repository Orchestration Patterns](https://daily.dev/posts/multi-agent-and-multi-repository-orchestration-patterns-5zzjjhndy) · Telerik · 1 upvotes · 0 comments - [Agentic Platform Engineering with GitHub Copilot](https://daily.dev/posts/agentic-platform-engineering-with-github-copilot-1xc31dz7v) · DevBlogs · 3 upvotes · 0 comments - [One Hub, 34 Clusters: Lessons From a GitOps Control Plane at Scale](https://daily.dev/posts/one-hub-34-clusters-lessons-from-a-gitops-control-plane-at-scale-dtajzlazo) · Cloud Native Now · 0 upvotes · 0 comments --- Tags: [#cicd](https://daily.dev/tags/cicd), [#platform-engineering](https://daily.dev/tags/platform-engineering), [#gitops](https://daily.dev/tags/gitops), [#ansible](https://daily.dev/tags/ansible) [View this post on daily.dev](https://daily.dev/posts/federated-multi-cluster-ansible-automation-platform-with-gitops-hoyxx8x0g) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Federated multi-cluster Ansible Automation Platform with GitOps","url":"https://daily.dev/posts/federated-multi-cluster-ansible-automation-platform-with-gitops-hoyxx8x0g","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/federated-multi-cluster-ansible-automation-platform-with-gitops-hoyxx8x0g"},"datePublished":"2026-10-30T13:34:42.947Z","dateModified":"2026-10-30T13:35:09.610Z","description":"A GitOps pattern lets platform teams run Red Hat Ansible Automation Platform across multiple clusters without a single point of failure. Git becomes the source...","image":"https://media.daily.dev/image/upload/s--1KxV4ohY--/f_auto/v1722860400/public/Placeholder%2007","thumbnailUrl":"https://media.daily.dev/image/upload/s--1KxV4ohY--/f_auto/v1722860400/public/Placeholder%2007","isAccessibleForFree":true,"articleSection":"Red Hat Developer","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Red Hat Developer","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/2a8895f3216c4900bdc455585a4ad3e4","url":"https://daily.dev/sources/rhdev"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/federated-multi-cluster-ansible-automation-platform-with-gitops-hoyxx8x0g","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"cicd,platform-engineering,gitops,ansible","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Red Hat Developer","item":"https://daily.dev/sources/rhdev"},{"@type":"ListItem","position":3,"name":"Federated multi-cluster Ansible Automation Platform with GitOps"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/federated-multi-cluster-ansible-automation-platform-with-gitops-hoyxx8x0g#faq","mainEntity":[{"@type":"Question","name":"How can I run Red Hat Ansible Automation Platform across multiple clusters without downtime during maintenance?","acceptedAnswer":{"@type":"Answer","text":"Use a federated multi-cluster deployment managed through GitOps, where Git repositories act as the single source of truth. Pushing to the main branch triggers a playbook (configure_aap.yml) that configures all gateways, such as AAP-Platform-DC1 and AAP-Platform-DC2, letting teams divert workloads to one datacenter while performing OS upgrades on nodes in another without service interruption. Teams designing zero-downtime automation platforms can track GitOps patterns like this on daily.dev."}},{"@type":"Question","name":"How does round-robin job dispatch work across multiple Ansible Automation Platform clusters?","acceptedAnswer":{"@type":"Answer","text":"Setting the target_aap variable to 'auto' in deploy_job.yml makes job execution alternate evenly across cluster instances using a GitHub index round-robin algorithm. Setting target_aap to an explicit value like dc1 or production instead filters gateway labels to target that specific environment. In production, dedicated infrastructure such as an F5 load balancer typically handles the actual load balancing. Engineers building multi-cluster automation routing can compare approaches like this on daily.dev."}}]} ```