Create an EKS cluster w Nginx-ingress & Argo-cd using Terraform

In this repo I created a simple EKS cluster w 3 nodes using Terraform and used Helm_provider to create nginx-ingress and argo-cd.

Authors

• @Amitk3293

Prerequisites

• Terraform >= 0.15, < 2.0.0
• AWS account
• A configured AWS CLI w the relevant IAM permissions ("TF-API-admin" in that case)
• IAM user w the relevant permissions
• kubectl
• wget (required for the eks module)
• S3 buckets for TF-remote-backend (optional)

Deployment

Clone the repo

  git clone https://github.com/Amitk3293/terraform2eks-w-argo-nginx-ingress.git

Edit eks-cluster.tf w the required eks settings and variables.tf and fill the requird region and cluster name

variable "region" {
  default     = "eu-central-1"
  description = "AWS region"
}

variable "cluster_name" {
  description = "EKS Cluster Name"
  default     = "eks-0001"

}

*Edit backend.tf w your remote backend to keep your state file sensitive data being "safe" or delete to use a local backend

Initiallize Terraform, plan and apply

terraform init
terraform plan
terraform apply

When TF process ends successfully configure kubeconfig to be able to use kubectl

aws eks --region $(terraform output -raw region) update-kubeconfig --name $(terraform output -raw cluster_name)

using Terraform-helm provider

For deploy nginx-ingress using Helm_provider go to /helm-tf/modules/nginx-ingress

**Edit backend.tf w your remote backend to keep your state file "safe" or delete to use a local backend

Initiallize Terraform, plan and apply

terraform init
terraform plan
terraform apply

When TF process ends successfully - Get the ingress service to have your ingress external IP

k get svc -n ingress
NAME                                 TYPE           CLUSTER-IP       EXTERNAL-IP                                                                 PORT(S)                      AGE
ingress-nginx-controller             LoadBalancer   172.20.219.188   a1ceeff3173e8452ab3b1b5c42b60069-404761402.eu-central-1.elb.amazonaws.com   80:31114/TCP,443:31853/TCP   54s
ingress-nginx-controller-admission   ClusterIP      172.20.44.234    <none>                                                                      443/TCP                      54s

For deploy argo-cf using Helm_provider go to /helm-tf/modules/argo-cd

Edit argo-values.yaml hosts to argo-cd.

server:
  extraArgs:
    - --insecure
  ingress:
    enabled: true
    hosts:
      - argo-cd.amitk.link
    ingressClassName: nginx
    paths:
      - /

you can switch the parameter

     hosts:
      - argo-cd.<your-domain>

**Edit DNS Cname record with a record name- argo-cd. and a value of the ingress external IP we check before.

Initiallize Terraform, plan and apply

terraform init
terraform plan
terraform apply

browse to argo-cd.

amitk@pop-os ~ curl -I argo-cd.amitk.link
HTTP/1.1 200 OK
Date: Sun, 06 Mar 2022 19:33:25 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 843
Connection: keep-alive
Accept-Ranges: bytes
X-Frame-Options: sameorigin
X-Xss-Protection: 1

To sync your application w argo-cd run

helm get manifest ingress-nginx -n ingress
helm get manifest argo-cd -n argo-cd

and add the helm manigest output to a file named ingress.yaml or argo-cd.yaml outputs into application-charts/templates/app-folder/ folder in the repo. Then log in to ArgoCD and sync the git repo and application-charts/templates/ path.

• check Screenshots folder to see the result