Kubernetes is a powerful tool. It can help you manage complex applications and provide you with the ability to easily automate tasks involved in managing them. In this course, we will start exploring Kubernetes from a beginner's standpoint. We will discuss what Kubernetes is and what it does, and we will work with some of the basic functionality of Kubernetes hands-on. We will build a simple Kubernetes cluster. We will also deploy a sample microservice application to the cluster in order to explore how Kubernetes can help easily manage such applications.

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"` was `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 removed Jenkins Deployment and, with it, 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"` was `deleted`.

Now, let's see what happened with the PersistentVolumes.

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

Even though we removed Jenkins Deployment and, with it, 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`?

In this lesson, we will play around 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