Jump right into Kubernetes development with career-focused lessons and hands-on practice.

DevOps for Developers

Kubernetes is a powerful container management tool that's taking the world by storm. This detailed course will help you master it.

In this course, you'll start with the fundamentals of Kubernetes and what the main components of a cluster look like. You'll then learn how to use those components to build, test, deploy, and upgrade applications, as well as how to achieve state persistence once your application is deployed. You'll also learn how to secure your deployments and manage resources, which are crucial DevOps skills.

By the time you're done, you'll have a firm grasp on what Kubernetes is, as well as the skills to deploy your own clusters and applications with confidence.

A Practical Guide to Kubernetes

# Deleting the Deployment
Let's delete the `jenkins` Deployment:

kubectl --namespace jenkins delete \
    deploy jenkins

The output shows us that the `deployment "jenkins"` is `deleted`.

Did anything happen with the PersistentVolumeClaim and the PersistentVolume?

kubectl --namespace jenkins get pvc

kubectl get pv

The combined output of both commands is as follows:

NAME    STATUS VOLUME        CAPACITY ACCESS MODES STORAGECLASS   AGE
jenkins Bound  manual-ebs-02 5Gi      RWO          manual-ebs     57s

NAME          CAPACITY ACCESS MODES RECLAIM POLICY STATUS    CLAIM           STORAGECLASS REASON AGE
manual-ebs-01 5Gi      RWO          Retain         Available jenkins/jenkins manual-ebs          10m
manual-ebs-02 5Gi      RWO          Retain         Bound     jenkins/jenkins manual-ebs          10m
manual-ebs-03 5Gi      RWO          Retain         Available jenkins/jenkins manual-ebs          10m

Even though we have removed the Jenkins Deployment and the Pod that used the claim, both the PersistentVolumeClaim and PersistentVolumes are intact. The `manual-ebs-01` volume is still bound to the `jenkins` claim.

# Deleting the PersistentVolumeClaim
What would happen if we remove the PersistentVolumeClaim `jenkins`?

kubectl --namespace jenkins \
    delete pvc jenkins

The output shows that the `persistentvolumeclaim "jenkins"` is `deleted`.

Now, let’s see what happens to the PersistentVolumes:

Practice with the Deployment by removing the created resources and exploring the effects of removal.

Removing the Resources and Exploring the Effects

Deleting the Deployment

Deleting the PersistentVolumeClaim