The steps here cover how to provision your EKS cluster and container registry.
NOTE: You might have already performed some of the steps (such as installing tools) mentioned below. If so you can ignore those steps and move directly to Step 5
Fork this repository into your own GitHub account and then clone (your forked version) down to your local machine.
We'll use the AWS CLI to get information from the cluster. Follow this step if you haven't yet installed the AWS CLI.
To install this you can install manually by following these instructions or if you have a package manager you can use the instructions below:
Mac Homebrew
brew install awscli
Windows Chocolatey
choco install awscli
The kubectl tool will be utilised to interact with your Kubernetes (K8S) cluster.
You can install this manually by following this guide below:
https://kubernetes.io/docs/tasks/tools/install-kubectl/
Or alternatively if you use a package manager it can be installed using the package manager:
Homebrew
brew install kubernetes-cli
Chocolatey
choco install kubernetes-cli
You can verify that it has installed correctly by running
kubectl version --client --output=yaml
It should print something like the below:
clientVersion:
buildDate: "2023-01-18T15:51:24Z"
compiler: gc
gitCommit: 8f94681cd294aa8cfd3407b8191f6c70214973a4
gitTreeState: clean
gitVersion: v1.26.1
goVersion: go1.19.5
major: "1"
minor: "26"
platform: darwin/arm64
kustomizeVersion: v4.5.7
Before we go ahead and create your cluster its worth exploring the files.
Oh and before you explore, the files in this directory could have been named whatever we like. For example the outputs.tf file can have been called foo.tf - we just chose to call it that because it contained outputs. So the naming was more of a standard than a requirement.
vpc.tf
Provisions and creates the Virtual Private Cloud (remember those from session two) that your cluster will be placed in.
security-groups.tf
Creates the AWS security groups for the cluster.
eks-cluster.tf
Provisions all the resources (AutoScaling Groups, etc...) required to set up an EKS cluster using the AWS EKS Module.
outputs.tf
This file defines the outputs that will be produced by terraform when things have been provisioned.
versions.tf
Configures the terraform providers (in our case the AWS provider) and sets the Terraform version to at least 0.14.
terraform.tfvars
This contains the values for the variables utilised in the terraform files. Make sure that the region looks correct and the credentials-profile should be as per the entry in your ~/.aws/credentials that you set up after following the videos prior to session 3.
Optionally update the tfvars file and ensure that the credentials-profile should be as per the entry in your ~/.aws/credentials that you set up after following the videos prior to session 3.
We need to get terraform to pull down the AWS provider.
In order to do this run:
terraform init
NOTE: If you have any issues with Terraform initialise it could be that the versions from a previous run have now been updated. You can remove those versions by running:
rm -rf .terraform
And then retrying terraform init
You should see something similar to the below:
Initializing modules...
Initializing the backend...
Initializing provider plugins...
- Reusing previous version of hashicorp/random from the dependency lock file
- Reusing previous version of hashicorp/local from the dependency lock file
- Reusing previous version of hashicorp/null from the dependency lock file
- Reusing previous version of hashicorp/template from the dependency lock file
- Reusing previous version of hashicorp/kubernetes from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
Firstly run a plan to see if what Terraform decides will happen.
terraform plan
We can then create your cluster by applying the configuration.
terraform apply
Sit back and relax - it might take 10 mins or so to create your cluster. Perfect time to have a ☕️ or a chat together.
NOTE: Sometimes the terraform apply can intermittently hang when trying to setup your kubectl config. You'll see this because it will take over 20 mins to create the cluster and keep repeating the same step that it is waiting for. If you do experience this then simply hit Ctrl + C (to cancel the run) and then re-run terraform apply - it should identify that much of the items have been created and finish off with updating your kubeconfig.
(We're working on it...)
Once its finished it'll output something like the info below. Those outputs are defined in the outputs.tf file.
Apply complete! Resources: 53 added, 0 changed, 0 destroyed.
Outputs:
cluster_endpoint = "https://C5CC135B19D791072B60A325678379BE.gr7.eu-west-2.eks.amazonaws.com"
cluster_id = "devops-upskill-eks"
cluster_name = "devops-upskill-eks"
cluster_security_group_id = "sg-099d37e0a02ad6eae"
Once its done you'll have your Kubernetes cluster all ready to go!!!
kubectl is used to issue actions on our cluster.
We need to configure kubectl to be able to authenticate with your cluster.
To do this we use the AWS CLI to get the credentials. Notice how we reference the outputs in the command below.
NOTE Replace the terraform-iac part with whatever your AWS Credentials profile is called in ~/.aws/credentials
aws eks --region $(terraform output -raw region) update-kubeconfig --name $(terraform output -raw cluster_name) --profile terraform-iac
It should say something like:
Added new context arn:aws:eks:eu-west-2:1234567:cluster/devops-upskill-eks to /Users/user/.kube/config
You can now verify if kubectl can access your cluster.
Go ahead and see how many nodes are running:
kubectl get nodes
It should show something like:
NAME STATUS ROLES AGE VERSION
ip-10-0-1-216.eu-west-2.compute.internal Ready <none> 70s v1.19.6-eks-49a6c0
ip-10-0-2-161.eu-west-2.compute.internal Ready <none> 71s v1.19.6-eks-49a6c0
ip-10-0-2-186.eu-west-2.compute.internal Ready <none> 75s v1.19.6-eks-49a6c0
Now you can head back over to the README for the next stage which is pushing your docker images to your registry.