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.

Practice

1. What does the command kubectl delete pod my-pod do in Kubernetes?

easy

A. It removes the pod named 'my-pod' from the cluster.

B. It creates a new pod named 'my-pod'.

C. It lists all pods including 'my-pod'.

D. It updates the pod named 'my-pod'.

Solution

1. Step 1: Understand the command action

   The command kubectl delete is used to remove resources from the cluster.

2. Step 2: Identify the resource and name

   Here, the resource is a pod and the name is 'my-pod', so it deletes that specific pod.

3. Final Answer:

   It removes the pod named 'my-pod' from the cluster. -> Option A

4. Quick Check:

   kubectl delete pod my-pod = Remove pod [OK]

Hint: kubectl delete + resource + name removes that resource [OK]

Common Mistakes:

• Confusing delete with create or update commands
• Deleting without specifying resource name
• Using delete to list resources

2. Which of the following is the correct syntax to delete a deployment named web-app?

easy

A. kubectl destroy deployment web-app

B. kubectl remove deployment web-app

C. kubectl delete web-app deployment

D. kubectl delete deployment web-app

Solution

1. Step 1: Recall kubectl delete syntax

   The correct syntax is kubectl delete <resource> <name>.

2. Step 2: Match the resource and name order

   kubectl delete deployment web-app follows this order correctly: deployment web-app.

3. Final Answer:

   kubectl delete deployment web-app -> Option D

4. Quick Check:

   kubectl delete + resource + name = correct syntax [OK]

Hint: Always use 'kubectl delete resource name' syntax [OK]

Common Mistakes:

• Using wrong verbs like remove or destroy
• Swapping resource and name order
• Omitting resource type

3. What will be the output of the command kubectl delete service my-service if the service my-service exists?

medium

A. Error: service "my-service" not found

B. service "my-service" deleted

C. service "my-service" created

D. No resources found

Solution

1. Step 1: Understand delete command output

   When a resource is successfully deleted, kubectl confirms with a message like resource "name" deleted.

2. Step 2: Match output to existing resource

   Since my-service exists, the output confirms deletion.

3. Final Answer:

   service "my-service" deleted -> Option B

4. Quick Check:

   Deleting existing resource shows 'deleted' message [OK]

Hint: Successful delete shows 'resource "name" deleted' message [OK]

Common Mistakes:

• Expecting creation message on delete
• Confusing 'not found' error when resource exists
• Ignoring confirmation output

4. You run kubectl delete pod my-pod but get the error: error: resource(s) not found. What is the most likely cause?

medium

A. The pod 'my-pod' does not exist in the current namespace.

B. The pod 'my-pod' is already deleted but still shows in the list.

C. You used the wrong command; delete cannot remove pods.

D. The cluster is down and cannot process commands.

Solution

1. Step 1: Analyze the error message

   The error says resource not found, meaning the pod name is not found in the current namespace.

2. Step 2: Check common causes

   Most often, this happens because the pod does not exist or you are in the wrong namespace.

3. Final Answer:

   The pod 'my-pod' does not exist in the current namespace. -> Option A

4. Quick Check:

   Resource not found = pod missing or wrong namespace [OK]

Hint: Check namespace and pod name if resource not found error [OK]

Common Mistakes:

• Assuming delete cannot remove pods
• Ignoring namespace context
• Thinking cluster downtime causes this error

5. You want to delete all pods with the label app=frontend. Which command correctly deletes only those pods?

hard

A. kubectl delete -l app=frontend

B. kubectl delete pods --all

C. kubectl delete pods --selector app=frontend

D. kubectl delete pods app=frontend

Solution

1. Step 1: Understand label selector syntax

   To delete pods by label, use the --selector or -l flag with the label key=value.

2. Step 2: Identify correct command

   kubectl delete pods --selector app=frontend uses --selector app=frontend, which is the correct full flag. kubectl delete -l app=frontend uses -l but misses the resource type pods.

3. Step 3: Confirm other options

   kubectl delete pods --all deletes all pods, not filtered. kubectl delete pods app=frontend is invalid syntax.

4. Final Answer:

   kubectl delete pods --selector app=frontend -> Option C

5. Quick Check:

   Use --selector or -l to filter pods by label [OK]

Hint: Use --selector or -l flag to delete by label [OK]

Common Mistakes:

• Using --all deletes everything, not filtered
• Incorrect syntax without --selector or -l
• Confusing label with resource name