kubectl configuration for EKS in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the purpose of aws eks update-kubeconfig

What is the main purpose of running the command aws eks update-kubeconfig --name cluster_name?

A It upgrades the EKS cluster to the latest Kubernetes version.

B It deploys the Kubernetes cluster on AWS EKS.

C It deletes the existing kubeconfig file from the local machine.

D It creates or updates the local kubeconfig file with cluster access details for kubectl.

💡 Hint

Think about what kubectl needs to connect to a cluster.

The aws eks update-kubeconfig command fetches cluster details and updates the local kubeconfig file so kubectl can communicate with the EKS cluster.

❓ Configuration

intermediate

Correct kubectl context after updating kubeconfig

After running aws eks update-kubeconfig --name my-cluster, which command correctly switches kubectl to use the new EKS cluster context?

A kubectl config use-context my-cluster

B kubectl switch context my-cluster

C kubectl set context my-cluster

D kubectl config set-context default

💡 Hint

Look for the correct kubectl command to change context.

The kubectl config use-context command switches kubectl to the specified cluster context. The context name for EKS is usually the cluster name.

❓ Architecture

advanced

Role of IAM in kubectl authentication for EKS

Which statement best describes how IAM roles are used when configuring kubectl to access an EKS cluster?

A IAM roles provide temporary credentials that kubectl uses to authenticate with the EKS API server via the aws-iam-authenticator.

B IAM roles are not involved; kubectl uses static tokens stored in kubeconfig for authentication.

C IAM roles directly replace Kubernetes service accounts for pod permissions.

D IAM roles are only used for EC2 instances, not for kubectl access.

💡 Hint

Think about how AWS secures API access with temporary credentials.

kubectl uses the aws-iam-authenticator plugin which leverages IAM roles to generate temporary tokens for authenticating to the EKS API server.

❓ security

advanced

Securing kubeconfig file for EKS access

What is the best practice to secure your kubeconfig file that contains EKS cluster access information?

A Disable authentication in the kubeconfig file to simplify access.

B Share the kubeconfig file with all team members via email for easy access.

C Set file permissions to allow only the owner to read and write the kubeconfig file.

D Store the kubeconfig file in a public cloud storage bucket for backup.

💡 Hint

Think about who should have access to sensitive credentials.

Restricting kubeconfig file permissions prevents unauthorized users from accessing cluster credentials, enhancing security.

❓ service_behavior

expert

Effect of changing cluster endpoint in kubeconfig

If you manually edit the kubeconfig file to change the EKS cluster endpoint to an incorrect URL, what will happen when you run kubectl get pods?

A kubectl will connect to the wrong cluster and show pods from that cluster.

B kubectl will fail to connect and return a connection error.

C kubectl will ignore the endpoint and use a cached connection.

D kubectl will automatically correct the endpoint to the original URL.

💡 Hint

Consider what happens if the API server address is wrong.

kubectl relies on the endpoint URL to connect to the cluster API server. An incorrect URL causes connection failure.

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