royalt1234 / aws-eks-setup-terraform Goto Github PK

Quite recently, I was tasked with creating a production ready Kubernetes cluster from the ground up at Darey.io where I Learn DevOps via a Project Based Learning model. This task gave me a deep and practical insight into the technical structure and setup of Kubernetes. Though it took me a while, I was able to set it up as requested and as per documentation.

Moving forward with the added knowledge, I decided to set up an AWS EKS Cluster which I would use for some application deployments. This next tasks would center around deployments and persisting data in k8s. However, this article is only a guide to provisioning your own AWS EKS Cluster using IaC(Terraform). It is advisable to do this first with the console if you don't already have knowledge as to how it all works.

Terraform is the IaC tool for this guide(knowledge of terraform is a prerequisite for this process), below are the steps to follow in setting up your EKS Cluster using terraform on your control machine;

1. Setup a controller client machine(can be an EC2 instance or your local machine)

2. Install Terraform, Kubectl, AWSCLI, aws-iam-authenticator

3. Create a folder where you'd clone the Terraform repo already provide by Hashicorp/AWS

4. Clone down the [Github Repo] (https://github.com/hashicorp/terraform-provider-aws) into your controller client machine

5. cd into the folder, cd into examples dir, cd into eks-getting-started

6. ls to see the '.tf' files

7. Feel free editing to your preference, things such as Region, names, instance type for the worker nodes, version of Kubernetes among others.

8. Run terraform init to initialize the folder, terraform plan to see what resources would be created. 18 resources would be created in building this cluster. terraform apply to create the resources. It would take some 8-10 min for the cluster to be built and ready to go.

9. Now the cluster is built, you have to update the --kubeconfig with the awscli command

aws eks --region <region> update-kubeconfig --name <cluster-name>

10. Test that everything works by running a kubectl command(any kubectl command) to show the nodes in your cluster

kubectl get nodes -o wide