Deploying a Kubernetes cluster with Terraform, a CI/CD pipeline with Github actions and ArgoCD, and monitoring set up.

To replicate this locally, clone the repo and do the following:

Set up an IAM user with Administrator privileges
Set your AWS credentials as environment variables
Make sure you already have a route53 hosted zone, add your domain name and subdomain names in the terraform.tfvars file
Set the following terraform environment variables:

export TF_VAR_argoslack=""

export TF_VAR_prometheusslack=""

The ArgoCD login password to view the deployments. The password has to be bcrypt hashed

export $PASS=""
export TF_VAR_argopass=$(htpasswd -nbBC 10 "" $PASS | tr -d ':\n' | sed 's/$2y/$2a/')

You can also set these variables in Github Actions secrets.

Live links

My sock-shop is hosted on sock.sarahligbe.live
My portfolio is hosted on portfolio.sarahligbe.live
ArgoCD is hosted on argocd.sarahligbe.live (username = admin)
Grafana is hosted on graf.sarahligbe.live (username = admin) Prometheus is hosted on prom.sarahligbe.live

The links no longer work. I destroyed the infrastructure

For this project, I set up:

A VPC with public, private and intra subnets. The intra subnets were to be assigned to the Control plane, while the Worker nodes were in the private subnet.
Karpenter for autoscaling
Cert manager and Let's Encrypt for SSL
Nginx ingress to route traffic from the pods to the internet
Prometheus and Grafana for monitoring
Loki for logging
Github Actions for CI
ArgoCD for continuous deployment of the applications in the kubernetes cluster.

The Infrastructure directory contains the terraform script to set up the EKS cluster and install cert-manager, nginx ingress controller, karpenter, prometheus, grafana, and loki. Github actions does the CI and sets this directory up.

You can delete the backend in the providers.tf file to run it locally or use your own s3 backend.

The K8s directory contains the applications - the sockshop microservice app and the portfolio app. It also contains the grafana dashboard for to monitor the sockshop performance. ArgoCD does the CD and sets this directory up. I used the ArgoCD Application set to set up the CD since I was deploying more than one application.