GitOps: CI/CD using GitHub Actions and ArgoCD on Kubernetes
Deploying Helm Charts on AWS EKS Cluster using ArgoCD and GitOps
GitOps is one of the hottest topics in the world of DevOps as it’s an evolution of Infrastructure as Code (IaC) and a DevOps best practice that leverages Git as the single source of truth, and control mechanism for creating, updating, and deleting system architecture. More simply, GitOps is a way of implementing Continuous Deployment for cloud-native applications.
In today’s Agile world, modern applications are developed with speed and scale in mind, and in the actual world we deploy code to production hundreds of times per day, so to accomplish this we need to acquire DevOps best practices like GitOps is one of them as it works on the declarative approach.
In this article, instead of talking much about what is GitOps, I will show you how to implement it by setting up a real-world CI/CD workflow with GitHub Actions and ArgoCD which is a very famous GitOps tool built to deploy applications to Kubernetes. And it is just another way to implement GitOps.
Note: In this article, I have used AWS EKS Cluster, if you don’t know how to create one then you can refer to this article of mine, in this, I have explained everything from scratch.
