Part 1: Terraform scripts for the Kubernetes cluster.

Terraform is used to provison both EKS kubernetes Infrastructure & deploy Kubernetes app

Terraform is a free and open-source infrastructure as code (IAC) that can help to automate the deployment, configuration, and management of the remote servers. Terraform can manage both existing service providers and custom in-house solutions.

This terraform github repo deploys simple nginx application in EKS cluster

Create the Kubernetes deployment using "nginx" image with replicas=2 in node_group_one
Create a service of type=LoadBalancer to expose app for simple external access
initContainer of deployment used to manipulate /usr/share/nginx/html/index.html to display
Welcome to POD:<pod-name> NODE:<node-name> NAMESPACE:<namespace> POD_IP:<pod-ip>

Desired Output:

Prerequisites:

EKS access
Basic understanding of AWS, Terraform & Kubernetes
GitHub Account

Part 1: Terraform scripts for the Kubernetes cluster.

Step 1: Create .tf file for accessing EKS cluster tfstate

Create providers.tf file and add below content in it to access remote s3 backend

data "terraform_remote_state" "eks" {
  backend = "s3"

  config = {
    bucket = "bijubayarea-s3-remote-backend-deadbeef"
    key    = "test-terraform-eks-cluster/terraform.tfstate"
    region = var.region
  }
}

Retrieve EKS cluster information

provider "aws" {
region                   = data.terraform_remote_state.eks.outputs.region
shared_credentials_files = ["~/.aws/credentials"]
profile                  = "vscode-user"
}

data "aws_eks_cluster" "cluster" {
  name = data.terraform_remote_state.eks.outputs.cluster_id
}

Step 2: Create .tf file for storing Kubernetes provider

Create providers.tf file and add below content in it

provider "kubernetes" {
  host                   = data.aws_eks_cluster.cluster.endpoint
  cluster_ca_certificate = base64decode(data.aws_eks_cluster.cluster.certificate_authority.0.data)
  exec {
    api_version = "client.authentication.k8s.io/v1beta1"
    command     = "aws"
    args = [
      "eks",
      "get-token",
      "--cluster-name",
      data.aws_eks_cluster.cluster.name
    ]
  }
}

Step 3: Create .tf file for K8s deployment : NGINX webserver

Create k8s-deployment.tf file for VPC and add below content in it

Below in yaml format for easier readabilty (But terraform code used to deploy)

spec:
    initContainers:
    - name: nginx-init        
      image: busybox:1.28
  	    
      env:
      - name: MY_NODE_NAME
        valueFrom:
          fieldRef:
            apiVersion: v1
            fieldPath: spec.nodeName
      - name: MY_POD_NAME
        valueFrom:
          fieldRef:
            apiVersion: v1
            fieldPath: metadata.name
      - name: MY_POD_NAMESPACE
        valueFrom:
          fieldRef:
            apiVersion: v1
            fieldPath: metadata.namespace
      - name: MY_POD_IP
        valueFrom:
          fieldRef:
            apiVersion: v1
            fieldPath: status.podIP
      command:
      - sh
      - -c
      - echo Welcome to POD:$(MY_POD_NAME) NODE:$(MY_NODE_NAME) NAMESPACE:$(MY_POD_NAMESPACE)
        POD_IP:$(MY_POD_IP)> /work-dir/index.html
      
      volumeMounts:
      - mountPath: /work-dir
        mountPropagation: None
        name: workdir

create k8s deployment "nginx" with replicas=2
pod containers: one is initContainer=nginx-init and container=nginx-pod-node
intContainer used to get environment variables: POD_NAME and NODE_NAME and write to /usr/share/nginx/html/index.html

pod ephemeral volume EmptyDir is attached to pod and mounted on both containers

containers:
    - name: nginx-pod-node
      image: nginx:1.7.8
      ports:
      - containerPort: 80
        protocol: TCP
      resources:
        limits:
          cpu: 500m
          memory: 512Mi
        requests:
          cpu: 250m
          memory: 50Mi
      volumeMounts:
      - mountPath: /usr/share/nginx/html
        mountPropagation: None
        name: workdir
    
    volumes:
    - emptyDir: {}
      name: workdir

Step 4: Create .tf file to expose k8s deploy as service=Loadbalancer

Create k8s-service.tf file for k8s service and add below content in it

Below in yaml format for easier readabilty (But terraform code used to deploy)

apiVersion: v1
kind: Service
metadata:
  name: nginx-service
spec:
  ports:
  - nodePort: 31754
    port: 80
    protocol: TCP
    targetPort: 80
  selector:
    App: nginx-pod-node
  type: LoadBalancer

Step 5: Create .tf file for outputs for K8s LoadBalancer

Create outputs.tf file and add below content in it

output "lb_ip" {
  value = kubernetes_service.nginx.status.0.load_balancer.0.ingress.0.hostname
}

output the name of the LoadBalancer.

Step 6: Store our code to GitHub Repository

store the code in the GitHub repository

Step 7: Initialize the working directory

Run terraform init command in the working directory, which will download all the necessary providers and all the modules

Step 8: Create a terraform plan

Run terraform plan command in the working directory, which will give the execution plan

Plan: 6 to add, 0 to change, 0 to destroy.
Changes to Outputs:
+ lb_ip           = (known after apply)

Step 9: Create the k8s app & service on EKS

Run terraform apply command in the working directory which will create the Kubernetes k8s deployment, service & load balancer
Terraform will create the below resources on EKS
k8s deployment
k8s service

Step 10: Check output of terraform apply

Output for terraform plan command

$ terraform output
lb_ip = "ac32240ec0119446cbbad59de348fd7e-2131601910.us-west-2.elb.amazonaws.com"

Step 11: Set kubeconfig to access EKS kubernetes cluster using kubectl

retrieve the access credentials for your cluster from output and configure kubectl

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

Step 12: Verify the resources on AWS

Navigate to your EKS cluster and verify the resources

k8s deployment:

$ kubectl get nodes
NAME                                       STATUS   ROLES    AGE   VERSION
ip-10-0-1-118.us-west-2.compute.internal   Ready    <none>   13h   v1.23.9-eks-ba74326
ip-10-0-2-251.us-west-2.compute.internal   Ready    <none>   13h   v1.23.9-eks-ba74326

$ kubectl get deploy nginx -o wide
NAME    READY   UP-TO-DATE   AVAILABLE   AGE   CONTAINERS       IMAGES        SELECTOR
nginx   2/2     2            2           9h    nginx-pod-node   nginx:1.7.8   App=nginx-pod-node

$ kubectl  get pods -o wide
NAME                    READY   STATUS    RESTARTS   AGE   IP           NODE                                       NOMINATED NODE   READINESS GATES
nginx-b4988fd99-5hvj8   1/1     Running   0          9h    10.0.1.100   ip-10-0-1-118.us-west-2.compute.internal   <none>           <none>
nginx-b4988fd99-pk2cz   1/1     Running   0          9h    10.0.2.90    ip-10-0-2-251.us-west-2.compute.internal   <none>           <none>

k8s service=LoadBalancer:

$ kubectl get svc -o wide
NAME            TYPE           CLUSTER-IP       EXTERNAL-IP                                                               PORT(S)        AGE   SELECTOR
kubernetes      ClusterIP      172.20.0.1       <none>                                                                    443/TCP        13h   <none>
nginx-service   LoadBalancer   172.20.146.252   ac32240ec0119446cbbad59de348fd7e-2131601910.us-west-2.elb.amazonaws.com   80:31754/TCP   9h    App=nginx-pod-node

$ kubectl describe svc nginx-service 
Name:                     nginx-service
Namespace:                default
Labels:                   <none>
Annotations:              <none>
Selector:                 App=nginx-pod-node
Type:                     LoadBalancer
IP Family Policy:         SingleStack
IP Families:              IPv4
IP:                       172.20.146.252
IPs:                      172.20.146.252
LoadBalancer Ingress:     ac32240ec0119446cbbad59de348fd7e-2131601910.us-west-2.elb.amazonaws.com
Port:                     <unset>  80/TCP
TargetPort:               80/TCP
NodePort:                 <unset>  31754/TCP
Endpoints:                10.0.1.100:80,10.0.2.90:80
Session Affinity:         None
External Traffic Policy:  Cluster
Events:                   <none>

Kubernetes cluster is ready
Verify access to NGINX application using browser or 'curl' command

Step 13: Access NGINX using 'curl' & browser

Access the NBINX server, confirm load balance fucntionality provided by k8s service

NBINX server displays POD_NAME, NODE_NAME, POD_NAMESPACE & POD_IP

$ curl -s ac32240ec0119446cbbad59de348fd7e-2131601910.us-west-2.elb.amazonaws.com
Welcome to POD:nginx-b4988fd99-pk2cz NODE:ip-10-0-2-251.us-west-2.compute.internal NAMESPACE:default POD_IP:10.0.2.90

$ curl -s ac32240ec0119446cbbad59de348fd7e-2131601910.us-west-2.elb.amazonaws.com
Welcome to POD:nginx-b4988fd99-5hvj8 NODE:ip-10-0-1-118.us-west-2.compute.internal NAMESPACE:default POD_IP:10.0.1.100

$ curl -s ac32240ec0119446cbbad59de348fd7e-2131601910.us-west-2.elb.amazonaws.com
Welcome to POD:nginx-b4988fd99-pk2cz NODE:ip-10-0-2-251.us-west-2.compute.internal NAMESPACE:default POD_IP:10.0.2.90

$ curl -s ac32240ec0119446cbbad59de348fd7e-2131601910.us-west-2.elb.amazonaws.com
Welcome to POD:nginx-b4988fd99-pk2cz NODE:ip-10-0-2-251.us-west-2.compute.internal NAMESPACE:default POD_IP:10.0.2.90

$ curl -s ac32240ec0119446cbbad59de348fd7e-2131601910.us-west-2.elb.amazonaws.com
Welcome to POD:nginx-b4988fd99-pk2cz NODE:ip-10-0-2-251.us-west-2.compute.internal NAMESPACE:default POD_IP:10.0.2.90

$ curl -s ac32240ec0119446cbbad59de348fd7e-2131601910.us-west-2.elb.amazonaws.com
Welcome to POD:nginx-b4988fd99-5hvj8 NODE:ip-10-0-1-118.us-west-2.compute.internal NAMESPACE:default POD_IP:10.0.1.100

Name		Name	Last commit message	Last commit date
Latest commit History 40 Commits
images		images
.gitignore		.gitignore
.terraform.lock.hcl		.terraform.lock.hcl
README.md		README.md
k8s-service.tf		k8s-service.tf
k8s_deployment.tf		k8s_deployment.tf
outputs.tf		outputs.tf
providers.tf		providers.tf
varaiables.tf		varaiables.tf
versions.tf		versions.tf

Navigation Menu

Repository files navigation

Terraform is used to provison both EKS kubernetes Infrastructure & deploy Kubernetes app

Part 1: Terraform scripts for the Kubernetes cluster.

About

Releases

Packages

Contributors

Languages

Folders and files

Latest commit

History

Repository files navigation

Terraform is used to provison both EKS kubernetes Infrastructure & deploy Kubernetes app

Part 1: Terraform scripts for the Kubernetes cluster.

About

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages