Deleting Pods

Part of the Introduction to Kubernetes section of Coddy's Terminal journey. Lesson 6 of 45.

When you no longer need a Pod, delete it by name:

kubectl delete pod web

Kubernetes confirms with pod "web" deleted. The container is stopped and the Pod disappears from the list.

List the Pods again and you get:

No resources found in default namespace.

A Pod started with kubectl run is on its own: once deleted, nothing brings it back. Later you will meet Deployments, which recreate Pods for you.

Deleting a Pod that does not exist is an error: Error from server (NotFound): pods "web" not found. Kubernetes tells you exactly which resource it could not find.

Challenge

Beginner

Start a Pod named web from the nginx image, delete it, then list the Pods to confirm it is gone.

Try it yourself

Terminal

Test yourself

This lesson includes a short quiz. Start the lesson to answer it and track your progress.

All lessons in Introduction to Kubernetes

1Introduction

What Is Kubernetes The Cluster

4Deployments

Creating A Deployment Scaling Deployments From Manifests Updating Images Rolling Back Recap - Deployment Manager

7Configuration

ConfigMaps Secrets Environment Variables Recap - Config Master

10Web Shop Project

Project Overview Write The Deployment

Expose The Shop

Scale And Update

Roll Back Safely

2Pods

Running A Pod Listing Pods Describing PodsDeleting PodsRecap - Pod Wrangler

5Services

Exposing A Deployment Service Types Endpoints Recap - Service Desk

8Namespaces & Jobs

Namespaces Working In A Namespace Jobs Recap - Namespace Navigator

11Final Challenges

Cluster Detective Full Rollout Pipeline Broken Deployment Triage

3Manifests

Writing A Manifest Labels Recap - Manifest Writer

6Debugging

Pod Logs Executing Commands Image Pull Errors Crash Loops Recap - Pod Doctor

9Output Formats

Wide And Name Output YAML Output JSONPath Recap - Output Explorer

Practice on your own: Terminal playground