β¨This repository containe the code of the kubernetes manifest files.
I've divided my Blog into four parts this is the 3rd part of the project. Please go through below blog to get more idea
- 3rd Blog: π Links
- When CircleCI notices any changes in the application code, it starts executing the jobs that we have set up. There are a total of four jobs:
- This job tests the code. After the test job is completed, CircleCI proceeds to the next job.
- Note: I didn't add this job to save time. π
- In the build job, CircleCI pulls the base Docker images and packages our application code inside the image.
- The push job pushes the newly generated images to Docker Hub with a new tag.
- After the successful completion of the push job, the last job is executed, which updates the Kubernetes manifest repository with the new tag. This enables ArgoCD to detect the change and apply it to the cluster.
By following this pipeline, we ensure that our application code is thoroughly tested, built into Docker images, and deployed with the updated manifest using the GitOps approach.
-
1st Blog: π Links
-
2nd Blog: π Links
-
4th Blog: π Links
This blog containe Three GitHub repository
-
Application code repo β‘οΈ Containe application code Links
-
Terraform code repo β‘οΈ Provisioning Amazon EKS Cluster using Terraform Links
-
Kubernetes manifest repo β‘οΈ this one
If you want to learn how i created this project, please go through my blogs. I've shared link of all the blogs above.π
π Thank you so much for reading..