kubectl CLI installation and configuration in Kubernetes - Commands & Configuration

Introduction

kubectl is a command-line tool that lets you talk to Kubernetes clusters. It helps you manage and control your applications running in Kubernetes by sending commands to the cluster.

When you want to create or delete applications in a Kubernetes cluster.

When you need to check the status of your running containers and pods.

When you want to update or change the configuration of your Kubernetes resources.

When you need to troubleshoot issues by viewing logs or describing resources.

When you want to switch between different Kubernetes clusters or namespaces.

Commands

Download the latest stable kubectl binary for Linux to your current directory.

Terminal

curl -LO https://dl.k8s.io/release/v1.27.3/bin/linux/amd64/kubectl

Expected Output

No output (command runs silently)

Make the downloaded kubectl binary executable so you can run it.

Terminal

chmod +x kubectl

Expected Output

No output (command runs silently)

Move the kubectl binary to a directory in your system PATH so you can run it from anywhere.

Terminal

sudo mv kubectl /usr/local/bin/

Expected Output

No output (command runs silently)

Check that kubectl is installed correctly and see its version.

Terminal

kubectl version --client

Expected Output

Client Version: v1.27.3

→

--client - Show only the client version without connecting to a cluster

Display the current Kubernetes configuration, showing clusters, users, and contexts kubectl knows about.

Terminal

kubectl config view

Expected Output

apiVersion: v1

clusters:

- cluster:

    server: https://example-cluster-api-server

  name: example-cluster

contexts:

- context:

    cluster: example-cluster

    user: example-user

  name: example-context

current-context: example-context

kind: Config

preferences: {}

users:

- name: example-user

  user:

    token: example-token

Key Concept

If you remember nothing else, remember: kubectl is your main tool to communicate with Kubernetes clusters by sending commands and managing configurations.

Common Mistakes

Not making the kubectl binary executable after downloading.

Without execute permission, the system won't let you run kubectl commands.

Always run 'chmod +x kubectl' after downloading the binary.

Not moving kubectl to a directory in the system PATH.

If kubectl is not in the PATH, you must specify its full path every time, which is inconvenient.

Move kubectl to /usr/local/bin or another PATH directory using 'sudo mv kubectl /usr/local/bin/'.

Running 'kubectl version' without '--client' before configuring access to a cluster.

kubectl tries to connect to a cluster and fails if no cluster is configured, causing confusing errors.

Use 'kubectl version --client' to check installation without needing cluster access.

Summary

Download the kubectl binary for your operating system.

Make the binary executable and move it to a directory in your system PATH.

Verify the installation by checking the client version.

View your current Kubernetes configuration with 'kubectl config view'.

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