Persistent Volume Claim
This guide has been reviewed and reformatted for Ruk-Com Cloud PaaS. Screens may vary slightly by platform version.
Click or tap a screenshot to view it at its original size.
Objective
This guide explains how to use Persistent Volume Claim on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.
Before you begin
- Sign in with an account permitted to manage the relevant environment.
- Confirm the target environment, region and resources before saving changes.
- Create a backup or rollback plan before changing a production system.
Every time your pod application needs to access a Persistent Volume (PV), it requests a specific # PersistentVolumeClaim (PVC) link with a specific storage and access mode. As such, the Ruk-Com PaaS is not limited to PVCs (includingcreation) However, there are a few things to keep in mind when working with continuous volume claims:
- If you specify a StorageClass other than Ruk-Com-dynamic-volume The default PV should be created in advance.
- When multiple pods should use the same PV, make sure that ROX or RWX AccessMode is supported.