kubectl configuration for EKS in AWS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is kubectl used for in EKS?

kubectl is a command-line tool that lets you communicate with your Kubernetes cluster on EKS. You use it to deploy apps, check cluster status, and manage resources.

beginner

What AWS CLI command helps update your kubectl config for EKS?

The command aws eks update-kubeconfig --name <cluster-name> updates your local kubectl config file to connect to your EKS cluster.

beginner

Where is the kubectl configuration file stored by default?

By default, the kubectl config file is stored at ~/.kube/config on your local machine.

intermediate

Why do you need IAM permissions to configure kubectl for EKS?

IAM permissions ensure you have the right to access the EKS cluster and update the kubectl config securely. Without proper permissions, you cannot connect to the cluster.

intermediate

What does the aws eks update-kubeconfig command do behind the scenes?

It fetches the cluster endpoint and certificate data, then writes these details into your kubectl config file so you can securely connect to the cluster.

Which command updates your local kubectl config to connect to an EKS cluster?

A kubectl update config --eks my-cluster

B kubectl config set-context my-cluster

C aws eks update-kubeconfig --name my-cluster

D aws configure set eks.cluster my-cluster

The correct command is aws eks update-kubeconfig --name my-cluster. It updates your local config with the cluster details.

Where is the default location of the kubectl config file?

A ~/.kube/config

B /etc/kubernetes/config

C /usr/local/kube/config

D ~/.aws/config

The kubectl config file is stored at ~/.kube/config by default.

What AWS service manages permissions needed to access EKS clusters?

A Amazon S3

B Amazon EC2

C AWS Lambda

D AWS IAM

AWS IAM manages user permissions and access control for EKS clusters.

What information does the update-kubeconfig command add to your config file?

A Cluster endpoint and certificate data

B User passwords

C EC2 instance IDs

D S3 bucket names

The command adds the cluster endpoint and certificate data to enable secure connection.

Why is it important to have the correct IAM permissions before configuring kubectl for EKS?

A To avoid paying extra AWS fees

B To ensure secure and authorized access to the cluster

C To speed up the cluster creation

D To enable automatic backups

Correct IAM permissions ensure you can securely and properly access the EKS cluster.

Explain the steps to configure kubectl to connect to an EKS cluster.

Think about how AWS CLI helps kubectl know about your cluster.

Describe why IAM permissions are critical when setting up kubectl for EKS.

Consider security and access control in AWS.

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