CI/CD Deployments with AWS CodeBuild and GitOps to EKS and AKS Kubernetes Clusters

In this video, I walk through how you can set up a full CI/CD pipeline for automated deployments to EKS and AKS Kubernetes clusters. I start off by explaining what GitOps is and then focus on how to set up a pipeline in AWS with CodeBuild and CodePipeline for the CI stage of the workflow. In the CI stage, I test my application, build and tag it before pushing it to Docker Hub. Once that is done, I use kustomize to update the Kubernetes manifest file for the application and then push this to a repo that the GitOps tool is watching. After that, I demonstrate how Fleet acts on the detected changes in the repository and deploys the application to EKS and AKS.
Timestamps:
0:00 - Introduction
00:25 - Overview
01:54 - Application Source Code & Dockerfile
04:48 - Terraform Source Code for CI with AWS CodeBuild
17:45 - Kustomize Configuration Files
20:36 - CodeBuild CI Configuration with the buildspec.yaml file
30:07 - Pipeline Failure
30:53 - Pipeline Success
32:50 - Review workloads successfully deployed to EKS and AKS
Relevant GitHub Repositories:
github.com/LukeMwila/ci-for-g...
github.com/LukeMwila/fleet-mu...
Connect:
GitHub: github.com/LukeMwila
Twitter: / luke9ine
Medium: / outlier.developer
SUSE & Rancher Community: community.suse.com
If you found this video helpful, please like the video and subscribe to the channel!

[@ayencoscolfield3312]

Nice job and very well explained ,just seen your channel for the first time and your work is awesome, please keep up the good work

[@shaikzoheb3430]

Next level video. Amazing

[@chibezagomajnr3683]

Very insightful

[@sab311]

Thanks!

[@softwareengineer5764]

Hi Lukonde, I hope you are fine. This is an amazing guide for CI/CD pipeline. I need help here. If i am working on fullstack app. working with for example node, react, mongdb so If I take it as a reference guide and want to make this pipeline for production. Should I make separate frontend-pipeline from the backend? Second if I make Dev, Stage and Prod environment should I create 3 different clusters for each environment? Plz guide me. I am grateful for your videos. 👏👏😊😊😊

[@LukondeMwila]

Hi there, thanks a lot for your feedback. I'm very glad to hear the videos are helpful to you. If your application tiers are decoupled then I would say that you should have separate deployment streams for each of them (frontend, backend, etc). You want to be able to roll out new versions for each without having to upgrade each tier. As for the cluster model, you can either have a single cluster and separate your environments by namespace, or have a cluster per environment. Both have pros and cons. The first approach (cluster with namespace envs) will require more work to ensure secure isolation between the namespaces and the right amount of resource utilisation. However, it is cheaper than running 3 clusters. The latter is more expensive but provides better isolation which is really good for a prod env. So you can weigh up the pros and cons and see which works better for your context depending on the application, the risks, the effort in optimising your cluster and your budget for cluster management.