Software Engineering
How To Build A GitOps Pipeline On A Stack Of AWS Services
Using ArgoCD and other AWS services like CodeCommit, CodePipeline, CodeBuild, Amazon EKS
In this post, we’ll look into how to build a GitOps pipeline to deploy applications on Amazon EKS (Elastic Kubernetes Service). We’ll use ArgoCD and various AWS services like CodeCommit, CodePipeline, CodeBuild, and Amazon Elastic Container Registry (ECR).
Sometime back, I had written a post on GitOps and some of the challenges that we typically encounter, and a few key points to consider before adopting GitOps. Feel free to take a look if you are looking for a quick refresher.
Or, if you are new to GitOps, take a few minutes to go through the post as well before we look into more implementation specific details in this post.
And, if you want to dive deeper, refer Weaveworks blogs as well.
Picking The Tools
Although GitOps for Kubernetes can be achieved with FluxCD or ArgoCD, I have chosen ArgoCD for this post primarily because ArgoCD has an intuitive GUI that can help to interact and understand the GitOps pattern in a better way. This is not an issue for someone who likes the CLIs more than the GUIs.
