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.