In this article, I’ll walk through how I automated Argo CD configuration and microservices deployment on a Kubernetes cluster using Ansible.Why spend 5 minutes doing it when I can spend 5 days failing to automate it?Instead of manually installing Argo CD, applying manifests, and wiring everything step by step, the goal here is to make the setup repeatable, idempotent, and environment-friendly — something you can confidently run across clusters without worrying about human error.For this example, I’m using as the Kubernetes cluster. However, nothing in this approach is EKS-specific. You can follow along with (self-managed, GKE, AKS, kind, etc.) as long as your cluster credentials are available via:Ansible will use this kubeconfig to interact with the cluster and perform all required operations.This article focuses specifically on:Installing and configuring Bootstrapping GitOps using Deploying a via Argo CDIf you’re interested in the — including CI pipelines, container builds, and infrastructure provisioning — this setup is part of a larger workflow I’ve described here:Think of this article as a deep dive into the GitOps bootstrap layer, where Ansible acts as the glue between infrastructure and continuous delivery.Before we start configuring Argo CD using Ansible, make sure you have the following prerequisites in place.Ansible relies on Python, so ensure Python is installed.2. Clone the IaC RepositoryAll Ansible playbooks and configuration used in this article live in the following repository:git clone https://github.com/c0dysharma/microservices-demo-Iaac.gitcd microservices-demo-IaacThis repository contains:Ansible playbooks for Argo CD setupArgo CD Application manifestsSupporting configuration for automationInstall Ansible on your system.4. Install Kubernetes Ansible CollectionTo allow Ansible to interact with Kubernetes, install the official collection:ansible-galaxy collection install kubernetes.coreThis provides Ansible modules for managing Kubernetes resources using kubeconfig-based authentication.5. Install Python DependenciesSome Kubernetes modules require additional Python libraries.From inside the repository, install the dependencies:cd ansiblepip install -r requirements.txt6. Kubernetes Cluster Access (EKS)This setup assumes you’re coming from my previous article where the EKS cluster was already created.Configure kubeconfig access to your cluster:aws eks update-kubeconfig –name myapp-cluster –region Replace with your AWS region.This updates ~/.kube/config, allowing:kubectl to access the clusterAnsible to communicate with KubernetesRunning the Ansible PlaybookOnce the prerequisites are ready, we can use Ansible to:Configure on the clusterDeploy a microservice using Run the following command from the ansible/ directory:ansible-playbook argocd-installation.yamlThis playbook runs locally and uses your kubeconfig to interact with the cluster.Understanding the Ansible PlaybookBelow is a brief explanation of each task in the playbook and what it achieves.- name : Deploy ArgoCD hosts: localhostThe play runs on localhost because Ansible is acting as an orchestrator. All Kubernetes interactions happen via the kubeconfig — no SSH involved.1. Create the Argo CD Namespace- name : Create a k8s namespace kubernetes.core.k8s: api_version: v1 state: presentEnsures the argocd namespace existsKeeps Argo CD isolated from application workloads- name: Deploy argocd application kubernetes.core.k8s: src: https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml state: present wait: trueApplies the official Argo CD installation manifestInstalls all core components (API server, controller, repo-server, etc.)wait: true ensures resources are ready before continuing- name: Change argocd-server service to LoadBalancer kubernetes.core.k8s: kind: Service namespace: argocd definition: type: LoadBalancerChanges the Argo CD server service to LoadBalancerMakes the UI accessible externallySuitable for cloud environments like AWS EKSIn production, this is often replaced with Ingress + authentication.4. Deploy Application via Argo CD- name: Deploy Application using argocd kubernetes.core.k8s: src: ../argocd/application.yaml state: presentThis is where GitOps actually begins.Applies an Argo CD Application manifestThe application definition lives in GitArgo CD takes over continuous reconciliationFrom this point onward, Git becomes the source of truth.Verifying the Installation1. Verify Kubernetes ResourcesArgo CD components are deployed in the argocd namespaceThe application is deployed in the default namespacekubectl get pods -n argocdkubectl get pods -n defaultAll pods should be in a Running or Healthy state.Retrieve the Argo CD server endpoint:kubectl get svc argocd-server -n argocdOpen the external hostname or IP in your browser.3. Get Argo CD Admin CredentialsRetrieve the initial admin password:argocd admin initial-password -n argocd: output of the command handles one-time cluster bootstrap owns continuous deliveryApplication deployments are fully Manual kubectl apply steps are eliminated after setupThis pattern scales well as your platform grows and keeps responsibilities clearly separated between infrastructure automation and application delivery.From here, you can extend this setup with:Ingress + authentication for Argo CDMulti-environment GitOps (dev/staging/prod)Progressive delivery using Argo Rollouts