kubectl CLI installation and configuration in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Check kubectl version output

What is the output of the command kubectl version --client --short immediately after a successful kubectl installation?

Kubernetes

kubectl version --client --short

A Client Version: v1.27.0

B Error: unknown command "version" for "kubectl"

C Client Version: 1.27

D The connection to the server localhost:8080 was refused

💡 Hint

The command shows the client version in a short format.

The command kubectl version --client --short outputs the client version in a short, readable format like 'Client Version: v1.27.0'. Other options indicate errors or incomplete version info.

❓ Configuration

intermediate

Correct kubeconfig file location

After installing kubectl, where should the default kubeconfig file be placed for kubectl to automatically use it?

A /etc/kubernetes/kubeconfig.yaml

B ~/.kube/config

C /usr/local/bin/kubeconfig

D ~/.kubectl/config.yaml

💡 Hint

kubectl looks for the config file in a hidden directory inside your home folder.

By default, kubectl looks for the kubeconfig file at ~/.kube/config. Other locations require explicit environment variable settings.

❓ Troubleshoot

advanced

Diagnose kubectl connection error

You run kubectl get pods and get the error: The connection to the server localhost:8080 was refused. What is the most likely cause?

A kubectl binary is corrupted and cannot connect

B The Kubernetes API server is running but rejecting requests

C kubectl is not configured with a valid kubeconfig file or cluster context

D The pod names are misspelled in the command

💡 Hint

This error usually means kubectl tries to connect to localhost because it has no cluster info.

If kubectl cannot find a valid kubeconfig or context, it defaults to localhost:8080 which usually has no server running, causing this error.

🔀 Workflow

advanced

Set a specific context for kubectl

Which command correctly sets the current context to production-cluster in kubectl?

A kubectl config set current-context production-cluster

B kubectl set context production-cluster

C kubectl switch context production-cluster

D kubectl config use-context production-cluster

💡 Hint

The command uses 'config' and 'use-context' keywords.

The correct command to switch context is kubectl config use-context <context-name>. Other options are invalid commands.

✅ Best Practice

expert

Secure kubectl configuration best practice

What is the best practice to securely manage kubectl access credentials on a shared workstation?

A Store kubeconfig files with minimal permissions and use environment variables to specify them

B Keep kubeconfig files in a public folder for easy access

C Embed credentials directly in deployment YAML files

D Share a single kubeconfig file among all users without restrictions

💡 Hint

Think about file permissions and environment isolation.

Storing kubeconfig files with restricted permissions and specifying them via environment variables limits exposure and prevents accidental credential leaks.

Practice

1. What is the primary purpose of the kubectl command-line tool in Kubernetes?

easy

A. To manage and control Kubernetes clusters from your computer

B. To build Docker container images

C. To monitor server hardware performance

D. To write Kubernetes YAML configuration files

Solution

1. Step 1: Understand kubectl's role

   kubectl is designed to interact with Kubernetes clusters, allowing users to deploy, inspect, and manage resources.

2. Step 2: Differentiate from other tools

   Building Docker images or monitoring hardware are not functions of kubectl. Writing YAML files is done manually or with editors, not by kubectl.

3. Final Answer:

   To manage and control Kubernetes clusters from your computer -> Option A

4. Quick Check:

   kubectl manages clusters = D [OK]

Hint: kubectl controls Kubernetes clusters directly [OK]

Common Mistakes:

• Confusing kubectl with Docker commands
• Thinking kubectl builds container images
• Assuming kubectl edits YAML files automatically

2. Which of the following commands correctly downloads the latest stable kubectl binary for Linux and makes it executable?

easy

A. curl -O https://kubernetes.io/download/kubectl && chmod +x kubectl

B. wget https://kubectl.io/latest && chmod 777 kubectl

C. curl -LO https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl && chmod +x kubectl

D. apt-get install kubectl && chmod +x /usr/bin/kubectl

Solution

1. Step 1: Identify the official download URL and command

   curl -LO https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl && chmod +x kubectl uses the official Kubernetes release URL with a command to get the latest stable version dynamically and downloads the Linux amd64 binary.

2. Step 2: Check command correctness and permissions

   curl -LO https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl && chmod +x kubectl also correctly applies chmod +x to make the binary executable. Other options use incorrect URLs or commands.

3. Final Answer:

   curl -LO https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl && chmod +x kubectl -> Option C

4. Quick Check:

   Official URL + chmod +x = A [OK]

Hint: Use official Kubernetes URLs with curl and chmod +x [OK]

Common Mistakes:

• Using wrong URLs that don't point to kubectl binaries
• Forgetting to make the binary executable
• Using package managers that don't have kubectl

3. After installing kubectl and setting your kubeconfig file, what will the command kubectl config current-context output?

medium

A. The version of the kubectl client installed

B. The name of the current Kubernetes cluster context in use

C. The list of all pods running in the cluster

D. The IP address of the Kubernetes master node

Solution

1. Step 1: Understand the purpose of kubectl config current-context

   This command shows which cluster context kubectl is currently set to use from the kubeconfig file.

2. Step 2: Differentiate from other commands

   Listing pods uses kubectl get pods, version uses kubectl version, and IP address is not shown by this command.

3. Final Answer:

   The name of the current Kubernetes cluster context in use -> Option B

4. Quick Check:

   current-context shows active cluster = C [OK]

Hint: current-context shows active cluster name [OK]

Common Mistakes:

• Confusing current-context with pod listing
• Expecting version info from this command
• Thinking it shows IP addresses

4. You run kubectl get pods but get the error: error: You must be logged in to the server (Unauthorized). What is the most likely cause?

medium

A. kubectl is not installed on your system

B. You typed the command incorrectly

C. The Kubernetes cluster is down

D. Your kubeconfig file is missing or has incorrect credentials

Solution

1. Step 1: Analyze the error message

   The error says you must be logged in, which means authentication failed.

2. Step 2: Identify the cause related to kubeconfig

   This usually happens when the kubeconfig file is missing, corrupted, or has wrong credentials, so kubectl cannot authenticate to the cluster.

3. Final Answer:

   Your kubeconfig file is missing or has incorrect credentials -> Option D

4. Quick Check:

   Unauthorized error means kubeconfig issue = B [OK]

Hint: Unauthorized means kubeconfig or credentials problem [OK]

Common Mistakes:

• Assuming kubectl is not installed from this error
• Thinking cluster is down without checking logs
• Blaming command syntax for authentication errors

5. You have multiple Kubernetes clusters and want to switch kubectl to use a different cluster context named dev-cluster. Which command correctly switches the context?

hard

A. kubectl config use-context dev-cluster

B. kubectl switch context dev-cluster

C. kubectl set context dev-cluster

D. kubectl change-context --cluster=dev-cluster

Solution

1. Step 1: Recall the correct command to switch contexts

   The official command to switch kubectl context is kubectl config use-context <context-name>.

2. Step 2: Verify other options are invalid

   Options B, C, and D are not valid kubectl commands and will cause errors.

3. Final Answer:

   kubectl config use-context dev-cluster -> Option A

4. Quick Check:

   Switch context uses 'config use-context' = A [OK]

Hint: Switch context with 'kubectl config use-context' [OK]

Common Mistakes:

• Using non-existent kubectl commands
• Confusing 'set' or 'change' with 'use-context'
• Forgetting to specify the exact context name