Part 5: Set up ArgoCD

EKS and Application repo

UpdatedMarch 4, 2026

Cloud & Infrastructure Engineer with 16+ years of experience in Azure, AWS & Hybrid IT environments. Passionate about DevOps, Automation, Terraform, CI/CD, and Enterprise Cloud Architecture. Building scalable, secure, and cost-optimized platforms. Based in Singapore 🇸🇬 | Sharing real-world hands-on cloud learnings.

Comments

Join the discussion

No comments yet. Be the first to comment.

DevSecOps Pipeline on AWS

Part 5 of 6

A step‑by‑step guide to building a secure, automated CI/CD pipeline on AWS using Jenkins, GitHub, Argo CD, Kubernetes, Prometheus, and Grafana. This series covers everything from code quality checks and vulnerability scanning to GitOps deployments and monitoring dashboards.

Up next

Part 6: Observability stack setup to monitor

Prometheus, Grafana and Helm

More from this blog

Designing an AI-Powered Smart Building Architecture on Azure

Azure Solution for SmartBuildings

May 5, 20264 min read32

Designing an AI-Powered Smart Building Architecture on Azure

10 RAG Architectures You Should Know in 2026

RAG

May 3, 20265 min read42

10 RAG Architectures You Should Know in 2026

Part 10: Environment Variables in Pipelines

Make it variables and reusable

Mar 18, 20263 min read24

Part 10: Environment Variables in Pipelines

Part 9: Parameterized Pipelines

Scaling pipeline to accept Dynamic inputs

Mar 18, 20263 min read11

Part 8: Multibranch Pipelines

Scaling with branches

Mar 11, 20263 min read15

ask-abhi

22 posts

Go to the Jenkins-master node and add our own EKS cluster to ArgoCD for application deployment using the CLI
Login to argoCD from CLI

argocd login 65.2.186.181:31797 --username admin

[Note] 65.2.186.181:31797 --> This should be your argocd url and after login enter your password

Check how many clusters are available in argocd

argocd cluster list

Get your cluster name

kubectl config get-contexts

Prepare the command to add your cluster to argocd and Enter

argocd cluster add iam-root-account@wanderlust.ap-southeast-1.eksctl.io --name wanderlust-eks-cluster

Note: Unknown possible due to sync issues, miss config or may takes some time, troubleshoot accordingly, continue to next and try later by readding again after connecting to repo in next step

Go to Settings --> Repositories and click on Connect your forked repo