Removing Resources and Exploring Effects
Practice with the Deployment by removing the created resources and exploring the effects of removal.
Deleting the Deployment
Let’s delete the jenkins
Deployment:
Press + to interact
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?
Press + to interact
kubectl --namespace jenkins get pvckubectl get pv
The combined output of both commands is as follows:
Press + to interact
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGEjenkins Bound manual-ebs-02 5Gi RWO manual-ebs 57sNAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGEmanual-ebs-01 5Gi RWO Retain Available jenkins/jenkins manual-ebs 10mmanual-ebs-02 5Gi RWO Retain Bound jenkins/jenkins manual-ebs 10mmanual-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
?
Press + to interact
kubectl --namespace jenkins \delete pvc jenkins
The output shows that the persistentvolumeclaim "jenkins"
is ...