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.