kubectl configuration for EKS in AWS - Mini Project: Build & Apply

kubectl configuration for EKS

📖 Scenario: You have created an Amazon EKS (Elastic Kubernetes Service) cluster. Now you want to configure your local kubectl tool to connect and manage this cluster.This project will guide you step-by-step to set up the kubectl configuration correctly for your EKS cluster.

🎯 Goal: By the end, you will have a valid kubectl configuration file that allows you to interact with your EKS cluster from your local machine.

📋 What You'll Learn

Use the AWS CLI to get cluster details

Create a kubeconfig file with the correct cluster info

Set the current context to the EKS cluster

Verify the configuration is complete and valid

💡 Why This Matters

🌍 Real World

Setting up kubectl configuration is essential to manage Kubernetes clusters on AWS EKS from your local machine.

💼 Career

Cloud engineers and DevOps professionals frequently configure kubectl to deploy and manage applications on EKS clusters.

1

Retrieve EKS cluster name

Create a variable called cluster_name and set it to the exact string my-eks-cluster which is the name of your EKS cluster.

AWS

# Create a variable called cluster_name and set it to 'my-eks-cluster'
# Your code here

Hint

The cluster name is a string. Use single quotes around it.

2

Set AWS region variable

Create a variable called region and set it to the exact string us-west-2 which is the AWS region where your EKS cluster is located.

AWS

cluster_name = 'my-eks-cluster'
# Create a variable called region and set it to 'us-west-2'
# Your code here

Hint

The region is a string. Use single quotes around it.

3

Generate kubeconfig command string

Create a variable called kubeconfig_command and set it to the exact string that runs the AWS CLI command to update your kubeconfig for the EKS cluster. The command should be: aws eks update-kubeconfig --name my-eks-cluster --region us-west-2 using the variables cluster_name and region with an f-string.

AWS

cluster_name = 'my-eks-cluster'
region = 'us-west-2'
# Create a variable kubeconfig_command with the AWS CLI update-kubeconfig command using f-string
# Your code here

Hint

Use an f-string to insert the variables into the command string.

4

Add command to run kubeconfig update

Add a line that uses the os module to run the kubeconfig_command string as a system command. First, import os at the top, then run os.system(kubeconfig_command).

AWS

cluster_name = 'my-eks-cluster'
region = 'us-west-2'
kubeconfig_command = f"aws eks update-kubeconfig --name {cluster_name} --region {region}"
# Import os and run os.system(kubeconfig_command)
# Your code here

Hint

Use import os at the top and then os.system(kubeconfig_command) to run the command.

Practice

1. What is the main purpose of the aws eks update-kubeconfig command?

easy

A. To delete an existing EKS cluster

B. To configure kubectl to connect to an EKS cluster

C. To create a new EKS cluster

D. To update the AWS CLI version

Solution

1. Step 1: Understand the command's function

   The aws eks update-kubeconfig command updates the local kubeconfig file to include connection details for an EKS cluster.

2. Step 2: Identify the purpose related to kubectl

   This allows kubectl to communicate with the specified EKS cluster for management tasks.

3. Final Answer:

   To configure kubectl to connect to an EKS cluster -> Option B

4. Quick Check:

   Configure kubectl = update-kubeconfig [OK]

Hint: Remember: update-kubeconfig sets kubectl for EKS access [OK]

Common Mistakes:

• Confusing update-kubeconfig with cluster creation
• Thinking it updates AWS CLI version
• Assuming it deletes clusters

2. Which of the following is the correct syntax to update your kubeconfig for an EKS cluster named my-cluster in region us-west-2?

easy

A. kubectl update config --cluster my-cluster --region us-west-2

B. aws eks create-kubeconfig --region us-west-2 --cluster my-cluster

C. aws eks update-kubeconfig --region us-west-2 --name my-cluster

D. aws eks config-update --name my-cluster --region us-west-2

Solution

1. Step 1: Recall the correct command and flags

   The correct command is aws eks update-kubeconfig with flags --region and --name to specify region and cluster name.

2. Step 2: Match the syntax to the options

   aws eks update-kubeconfig --region us-west-2 --name my-cluster matches the correct syntax exactly, while others use incorrect commands or flags.

3. Final Answer:

   aws eks update-kubeconfig --region us-west-2 --name my-cluster -> Option C

4. Quick Check:

   Correct syntax = aws eks update-kubeconfig --region us-west-2 --name my-cluster [OK]

Hint: Use --region and --name flags with update-kubeconfig [OK]

Common Mistakes:

• Using create-kubeconfig instead of update-kubeconfig
• Mixing kubectl commands with AWS CLI
• Incorrect flag names like --cluster or --config-update

3. After running aws eks update-kubeconfig --region us-east-1 --name test-cluster, what will be the output of kubectl config current-context?

medium

A. test-cluster

B. arn:aws:eks:us-east-1:123456789012:cluster/test-cluster

C. default

D. No context set

Solution

1. Step 1: Understand update-kubeconfig effect

   Running aws eks update-kubeconfig sets the current context in kubeconfig to the cluster name.

2. Step 2: Check kubectl current-context output

   The current context after update is the cluster name, here test-cluster.

3. Final Answer:

   test-cluster -> Option A

4. Quick Check:

   Current context = cluster name [OK]

Hint: Current context shows cluster name after update-kubeconfig [OK]

Common Mistakes:

• Expecting ARN instead of cluster name
• Assuming default context remains
• Thinking no context is set after update

4. You ran aws eks update-kubeconfig --region us-east-1 --name my-cluster but get an error: Unable to locate credentials. What is the most likely cause?

medium

A. kubectl is not installed

B. The region flag is misspelled

C. The cluster name is incorrect

D. AWS CLI is not configured with credentials

Solution

1. Step 1: Analyze the error message

   The error Unable to locate credentials means AWS CLI cannot find your access keys to authenticate.

2. Step 2: Identify the cause

   This usually happens if AWS CLI is not configured with credentials via aws configure or environment variables.

3. Final Answer:

   AWS CLI is not configured with credentials -> Option D

4. Quick Check:

   Missing AWS credentials cause this error [OK]

Hint: Check AWS CLI credentials setup if unable to locate credentials error [OK]

Common Mistakes:

• Assuming kubectl installation causes this error
• Blaming cluster name without checking credentials
• Ignoring region flag spelling

5. You want to configure kubectl to connect to two EKS clusters, clusterA in us-east-1 and clusterB in us-west-2. Which approach correctly sets up your kubeconfig to switch between these clusters?

hard

A. Run aws eks update-kubeconfig --region us-east-1 --name clusterA then aws eks update-kubeconfig --region us-west-2 --name clusterB, then use kubectl config use-context clusterB to switch

B. Run kubectl config set-context clusterA and kubectl config set-context clusterB manually without update-kubeconfig

C. Run aws eks create-cluster for both clusters, then kubectl auto-switches

D. Use aws eks update-kubeconfig only for one cluster and manually edit kubeconfig for the other

Solution

1. Step 1: Understand update-kubeconfig for multiple clusters

   Running aws eks update-kubeconfig multiple times adds each cluster's config to kubeconfig without overwriting.

2. Step 2: Switching contexts

   You can switch between clusters using kubectl config use-context with the cluster name as context.

3. Final Answer:

   Run update-kubeconfig for both clusters, then switch context with kubectl -> Option A

4. Quick Check:

   Multiple update-kubeconfig runs + use-context = multi-cluster setup [OK]

Hint: Run update-kubeconfig for each cluster, then switch context [OK]

Common Mistakes:

• Trying to create clusters instead of updating kubeconfig
• Manually editing kubeconfig without update-kubeconfig
• Assuming kubectl auto-switches clusters