Efficiently Delete Kubernetes Resources with kubectl delete

Kubectl is a powerful command-line tool used to interact with Kubernetes clusters. One of its essential capabilities is the ability to delete resources within the cluster efficiently using the delete command. This command allows administrators and developers to remove various Kubernetes objects such as pods, services, deployments, and more.

Let’s explore several examples of how to use kubectl delete effectively:

1. Deleting a specific pod named “nginx”:

kubectl delete pod nginx

This command deletes the pod named “nginx” from the cluster. To verify its execution, you can use kubectl get pods to check that the “nginx” pod no longer appears in the list of running pods.

2. Deleting all pods in a particular namespace, for example, “development”:

kubectl delete pod --all -n development

Here, --all specifies that all pods in the namespace “development” should be deleted. To confirm, use kubectl get pods -n development and verify that no pods are listed.

3. Removing a deployment named “frontend”:

kubectl delete deployment frontend

This command deletes the deployment named “frontend” along with its associated pods and services. To check, use kubectl get deployments to ensure that “frontend” deployment is no longer listed.

4. Deleting a service named “mysql-service”:

kubectl delete service mysql-service

This deletes the Kubernetes service named “mysql-service”. To verify, use kubectl get services and confirm that “mysql-service” is no longer present.

5. Deleting a namespace named “testing”:

kubectl delete namespace testing

This command removes the entire namespace “testing” and all resources within it. To ensure it’s deleted, use kubectl get namespaces and verify that “testing” is not listed.

6. Deleting a specific PersistentVolumeClaim (PVC) named “data-pvc”:

kubectl delete pvc data-pvc

This deletes the PersistentVolumeClaim “data-pvc”. To check, use kubectl get pvc and confirm that “data-pvc” is no longer visible.

7. Deleting a ConfigMap named “config”:

kubectl delete configmap config

This removes the ConfigMap “config”. To verify, use kubectl get configmaps and ensure “config” is no longer present.

8. Deleting a Secret named “api-secret”:

kubectl delete secret api-secret

This deletes the Secret “api-secret”. To confirm, use kubectl get secrets and check that “api-secret” is no longer listed.

9. Deleting a specific Job named “batch-job”:

kubectl delete job batch-job

This removes the Job “batch-job”. To verify, use kubectl get jobs and ensure “batch-job” is no longer present.

10. Deleting a Role named “admin-role”:

kubectl delete role admin-role

This deletes the Role “admin-role”. To check, use kubectl get roles and confirm that “admin-role” is no longer listed.

Also check similar articles.

Comprehensive Guide to kubectl get Command
Understanding Kubernetes Resources with kubectl explain
Setting Features on Kubernetes Objects using kubectl set
Running Docker Images on Kubernetes with kubectl run
Expose Kubernetes Services Easily with kubectl expose