kubectl delete for removal in Kubernetes - Step-by-Step Execution

Process Flow - kubectl delete for removal

User runs kubectl delete command

↓

kubectl sends delete request to API server

↓

API server processes delete request

↓

Resource marked for deletion

↓

Controller cleans up resource

↓

Resource removed from cluster

↓

kubectl shows confirmation message

This flow shows how the kubectl delete command removes a resource by sending a request to the Kubernetes API server, which then deletes the resource and confirms removal.

Execution Sample

Kubernetes

kubectl delete pod my-pod
kubectl delete deployment my-deployment

These commands delete a pod named 'my-pod' and a deployment named 'my-deployment' from the Kubernetes cluster.

Process Table

Step	Command	Action	API Server Response	Result
1	kubectl delete pod my-pod	Send delete request for pod 'my-pod'	Accepted	Pod 'my-pod' marked for deletion
2	API server	Process deletion	Success	Pod 'my-pod' removed from cluster
3	kubectl	Show confirmation	Deleted pod 'my-pod'	User sees success message
4	kubectl delete deployment my-deployment	Send delete request for deployment 'my-deployment'	Accepted	Deployment 'my-deployment' marked for deletion
5	API server	Process deletion	Success	Deployment 'my-deployment' removed from cluster
6	kubectl	Show confirmation	Deleted deployment 'my-deployment'	User sees success message
7	-	-	-	End of deletion commands

💡 All requested resources deleted successfully, kubectl confirms completion

Status Tracker

Resource	Initial State	After Delete Request	After Deletion	Final State
pod my-pod	Exists in cluster	Marked for deletion	Deleted	Does not exist
deployment my-deployment	Exists in cluster	Marked for deletion	Deleted	Does not exist

Key Moments - 2 Insights

Why does kubectl show a confirmation message after deletion?

kubectl waits for the API server to confirm the resource is deleted before showing the message, as seen in execution_table rows 3 and 6.

What happens if the resource does not exist when running kubectl delete?

kubectl will return an error from the API server indicating the resource was not found, so no deletion occurs. This is not shown in the current table but would stop at the API server step.

Visual Quiz - 3 Questions

Look at the execution table, what is the API server response after sending the delete request for 'my-pod'?

A Pending

B Accepted

C Rejected

D Error

💡 Hint

Check row 1 under 'API Server Response' column

At which step does the pod 'my-pod' get removed from the cluster?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Look at the 'Result' column in row 2

If the deployment 'my-deployment' was already deleted, what would change in the execution table?

A API server would respond with 'Accepted' anyway

B kubectl would show a success message

C API server would return an error indicating resource not found

D kubectl would retry deletion automatically

💡 Hint

Refer to key_moments about resource not existing

Concept Snapshot

kubectl delete <resource> <name>
- Sends delete request to Kubernetes API server
- API server marks resource for deletion
- Controller cleans up resource
- kubectl shows confirmation on success
- If resource missing, error returned

Full Transcript

The kubectl delete command removes Kubernetes resources by sending a delete request to the API server. The API server processes this request and marks the resource for deletion. Then, the controller cleans up the resource from the cluster. Once deleted, kubectl shows a confirmation message to the user. If the resource does not exist, kubectl will report an error. This process ensures resources are cleanly removed from the cluster.