INTRODUCTION TO NET
APPLICATION DEVELOPMENT
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
|
Provisioning, Binding, Using, Releasing, Reclaiming
|
|
|
Provisioning, Using, Binding, Releasing, Reclaiming
|
|
|
Provisioning, Reclaiming, Binding, Using, Releasing
|
|
|
Provisioning, Releasing, Binding, Using, Reclaiming
|
Detailed explanation-1: -Lifecycle Stages of a Persistent Volume and Claim. PVs and PVCs follow a lifecycle that starts with provisioning, moves on to binding, which is followed by using, and then can shift to reclaiming, retaining, and finally deletion.
Detailed explanation-2: -A PersistentVolumeClaim (PVC) is a request for storage by a user. It is similar to a Pod. Pods consume node resources and PVCs consume PV resources. Pods can request specific levels of resources (CPU and Memory).
Detailed explanation-3: -Reclaim policy When you no longer need a volume, you can delete the PVC objects, which allows the volume to be reclaimed. A reclaim policy of a PV tells the cluster what to do with the volume after it is released of its claim. Currently, volumes can either be retained, recycled, or deleted.
Detailed explanation-4: -Published November 16, 2022. Accidental PVC delete or namespace delete can cause the Persistent Volume to get deleted. Such volumes lose their data, and the stateful applications lose their state.
Detailed explanation-5: -Available–a free resource that is not yet bound to a claim. Bound–the volume is bound to a claim. Released–the claim has been deleted, but the resource is not yet reclaimed by the cluster. Failed–the volume has failed its automatic reclamation.
Detailed explanation-6: -Retain PVs. Derive new PVC manifests from existing PVCs. Delete old STS. Delete old PVCs. Allow reclaiming of PVs. Create new PVCs. Create new STS. 29-Sept-2021