Kubectl for cluster management in Azure - Step-by-Step Execution

Process Flow - Kubectl for cluster management

Start: User runs kubectl command

↓

kubectl parses command

↓

kubectl sends request to Kubernetes API Server

↓

API Server authenticates and authorizes request

↓

API Server processes request and updates cluster state

↓

kubectl receives response

↓

kubectl displays output to user

↓

End

kubectl takes your command, talks to the Kubernetes API server, which checks and updates the cluster, then kubectl shows you the result.

Execution Sample

Azure

kubectl get pods
kubectl describe pod mypod
kubectl delete pod mypod

These commands list pods, show details of a pod, and delete a pod in the cluster.

Process Table

Step	kubectl Command	Action	API Server Response	kubectl Output
1	kubectl get pods	Send GET request for pods list	List of pods returned	Displays list of pods
2	kubectl describe pod mypod	Send GET request for pod details	Details of 'mypod' returned	Displays pod details
3	kubectl delete pod mypod	Send DELETE request for pod 'mypod'	Pod 'mypod' deletion confirmed	Displays deletion confirmation
4	kubectl get pods	Send GET request for pods list	Updated list without 'mypod'	Displays updated pods list
5	-	-	-	End of commands

💡 All commands executed; cluster state updated accordingly.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Pods in cluster	['mypod', 'pod2']	['mypod', 'pod2']	['mypod', 'pod2']	['pod2']	['pod2']	['pod2']

Key Moments - 2 Insights

Why does 'kubectl get pods' show different results before and after deleting 'mypod'?

Because after the delete command (step 3), the pod 'mypod' is removed from the cluster state, so the next 'get pods' (step 4) shows the updated list without it.

Does kubectl itself delete pods or just send commands?

kubectl only sends commands to the Kubernetes API server; the API server performs the actual deletion and updates the cluster state, as shown in steps 3 and 4.

Visual Quiz - 3 Questions

Look at the execution table, what does kubectl display after the 'kubectl describe pod mypod' command?

A List of all pods in the cluster

B Confirmation that 'mypod' was deleted

C Details of the pod named 'mypod'

D Error message about 'mypod'

💡 Hint

Check row 2 under 'kubectl Output' in the execution table.

At which step does the pod 'mypod' get removed from the cluster according to the variable tracker?

A After Step 3

B After Step 2

C After Step 1

D After Step 4

💡 Hint

Look at the 'Pods in cluster' row in variable_tracker after each step.

If you run 'kubectl get pods' immediately after deleting 'mypod', what will you see?

A An empty list of pods

B The updated list without 'mypod'

C The pod 'mypod' still listed

D An error message

💡 Hint

Refer to step 4 in the execution_table and variable_tracker.

Concept Snapshot

kubectl sends commands to Kubernetes API server
API server authenticates and updates cluster state
kubectl shows results from API server
Common commands: get, describe, delete
Cluster state changes after delete
kubectl itself does not change state, only requests

Full Transcript

Kubectl is a tool to manage Kubernetes clusters. When you run a kubectl command, it sends a request to the Kubernetes API server. The API server checks your request, updates the cluster if needed, and sends back a response. Kubectl then shows this response to you. For example, 'kubectl get pods' lists all pods. 'kubectl describe pod mypod' shows details about one pod. 'kubectl delete pod mypod' removes that pod from the cluster. After deletion, running 'kubectl get pods' again shows the updated list without the deleted pod. Kubectl commands do not change the cluster directly; they ask the API server to do so.

Practice

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

easy

A. To manage and control Kubernetes clusters

B. To create virtual machines in Azure

C. To monitor network traffic outside the cluster

D. To write application code for Kubernetes

Solution

1. Step 1: Understand kubectl's role

   kubectl is designed to interact with Kubernetes clusters to manage resources like pods, deployments, and services.

2. Step 2: Compare options

   Options A, B, and C describe tasks unrelated to kubectl. Only To manage and control Kubernetes clusters correctly states its purpose.

3. Final Answer:

   To manage and control Kubernetes clusters -> Option A

4. Quick Check:

   kubectl = cluster management [OK]

Hint: kubectl controls Kubernetes clusters directly [OK]

Common Mistakes:

• Confusing kubectl with Azure VM tools
• Thinking kubectl writes application code
• Assuming kubectl monitors external network traffic

2. Which of the following is the correct syntax to list all pods in the current Kubernetes namespace using kubectl?

easy

A. kubectl get pods

B. kubectl list pods

C. kubectl show pods

D. kubectl describe pods

Solution

1. Step 1: Recall kubectl commands for listing resources

   The command to list resources is kubectl get, followed by the resource type.

2. Step 2: Evaluate options

   Only kubectl get pods uses the correct syntax kubectl get pods. Options A and B are invalid commands, and D shows detailed info, not a simple list.

3. Final Answer:

   kubectl get pods -> Option A

4. Quick Check:

   List pods = kubectl get pods [OK]

Hint: Use 'kubectl get' to list Kubernetes resources [OK]

Common Mistakes:

• Using 'list' or 'show' instead of 'get'
• Confusing 'describe' with listing
• Adding extra words after 'pods'

3. Given the command kubectl get pods -o wide, what extra information will you see compared to kubectl get pods?

medium

A. Detailed pod logs

B. Extended pod information including node and IP

C. Only pod names without status

D. List of services instead of pods

Solution

1. Step 1: Understand the '-o wide' option

   The -o wide flag shows additional columns like node name and pod IP address.

2. Step 2: Compare output differences

   Extended pod information including node and IP correctly describes the extra info. Detailed pod logs is about logs, not shown here. Only pod names without status is incorrect as status is shown by default. List of services instead of pods is unrelated.

3. Final Answer:

   Extended pod information including node and IP -> Option B

4. Quick Check:

   -o wide = more pod details [OK]

Hint: Use '-o wide' to see node and IP info for pods [OK]

Common Mistakes:

• Thinking '-o wide' shows logs
• Assuming it hides status info
• Confusing pods with services

4. You run kubectl get pod mypod but get an error saying the pod does not exist. What is the most likely cause?

medium

A. You are in the wrong namespace

B. The pod name is misspelled

C. The pod has already been deleted

D. All of the above

Solution

1. Step 1: Check common reasons for pod not found error

   The error can happen if the pod name is wrong, the pod was deleted, or you are looking in the wrong namespace.

2. Step 2: Evaluate options

   All options B, C, and D are valid causes. Therefore, All of the above which includes all is correct.

3. Final Answer:

   All of the above -> Option D

4. Quick Check:

   Pod not found = wrong namespace, name, or deleted [OK]

Hint: Check namespace, spelling, and pod existence [OK]

Common Mistakes:

• Ignoring namespace context
• Assuming pod always exists
• Not verifying pod name spelling

5. You want to update the image of a deployment named webapp to version v2 using kubectl. Which command correctly performs this update?

hard

A. kubectl update deployment webapp --image=webapp:v2

B. kubectl edit deployment webapp image=webapp:v2

C. kubectl set image deployment/webapp webapp=webapp:v2

D. kubectl change image webapp webapp:v2

Solution

1. Step 1: Identify the correct kubectl command to update deployment image

   The command kubectl set image is used to update container images in deployments.

2. Step 2: Analyze each option

   kubectl set image deployment/webapp webapp=webapp:v2 uses correct syntax: kubectl set image deployment/webapp webapp=webapp:v2. Options A, C, and D use invalid or incorrect commands.

3. Final Answer:

   kubectl set image deployment/webapp webapp=webapp:v2 -> Option C

4. Quick Check:

   Update image = kubectl set image [OK]

Hint: Use 'kubectl set image' to update deployment containers [OK]

Common Mistakes:

• Using 'kubectl update' which is invalid
• Trying 'kubectl edit' without proper syntax
• Using non-existent 'kubectl change' command