Skip to main content

Part 5: Set up ArgoCD

EKS and Application repo

Updated 2 min readMarkdown
Part of seriesDevSecOps Pipeline on AWS
Part 5: Set up ArgoCD
  • 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

[Note] Connection should be successful

  • Now, go to Applications and click on New App

[Important] Make sure to click on the Auto-Create Namespace option while creating argocd application

Congratulations, your application is deployed on the AWS EKS Cluster

  • Open ports 31000 and 31100 on the nodes of the EKS Cluster, and access it on a browser
<worker-public-ip>:31000

Email Notification

Next...


12 views

About the author

  • 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.

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 nextPart 6: Observability stack setup to monitorPrometheus, Grafana and Helm