< img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=3131724&fmt=gif" />
🚀 KubeSphere v4.1.2 with Enhancements and Bug Fixes is available now. Read the release notes for v4.1.2 → close
  • English
    • English
    • 简体中文
    1. 1.Create a KubeSphere Cloud account and log in to the platform.
    2. 2.In the upper-right corner, click Console, and then click Lite Cluster on the left.
    3. 3.Create a K8s cluster with KubeSphere installed.
    4. 4.Access KubeSphere with the default account and password (admin/P@88w0rd).
  •  Star
  1. Docs / 
  2. Documentation / 
  3. Cluster Management / 
  4. Storage / 
  5. Persistent Volume Claims / 
  6. View Persistent Volume List

Documentation

Last updated:
    Edit

    View Persistent Volume List

    This section introduces how to view the list of Persistent Volumes.

    Prerequisites

    You should join a cluster and have the Persistent Volume Claim Viewing permission within the cluster. For more information, refer to "Cluster Members" and "Cluster Roles".

    Steps

    1. Log in to the KubeSphere web console with a user who has the Persistent Volume Claim Viewing permission, and access your cluster.

    2. Click Storage > Persistent Volume Claims in the left navigation pane.

    3. On the Persistent Volume Claims page, click Persistent Volume to open the list of Persistent Volumes.

      • The Persistent Volume list provides the following information:

        Parameter Description

        Name

        The name, alias, and storage class of the Persistent Volume. Automatically provisioned Persistent Volumes have names generated by the system. For more information about storage classes, refer to the Storage Classes.

        Status

        The current status of the Persistent Volume.

        • Available: The Persistent Volume is not bound to any Persistent Volume claim. The KubeSphere web console currently does not support the direct creation of Persistent Volumes. If you create Persistent Volumes directly using backend command-line tools, the Persistent Volumes will have a status of Available. For more information, refer to the Kubernetes Documentation.

        • Bound: The Persistent Volume is already bound to a Persistent Volume claim.

        • Released: The Persistent Volume claim bound to the Persistent Volume has been deleted while the Persistent Volume itself has not been deleted.

        • Failed: The Persistent Volume encountered an unknown error.

        Capacity

        The capacity of the backend storage area.

        Access Modes

        The access modes of Persistent Volumes.

        • RWO (ReadWriteOnce): Allows a single node to read from and write to the Persistent Volume.

        • ROX (ReadOnlyMany): Allows multiple nodes to read from the Persistent Volume.

        • RWX (ReadWriteMany): Allows multiple nodes to read from and write to the Persistent Volume.

        Reclaim Policy

        The reclaim policy of the Persistent Volume. KubeSphere defaults to the Delete reclaim policy, which means that when the Persistent Volume claim is deleted, the Persistent Volume is also deleted. For more information, refer to the Kubernetes Documentation.

        Creation Time

        The creation time of the Persistent Volume.

      • Click the search box above the list and search for Persistent Volumes by name or status.

      • Click refresh in the upper right corner of the list to refresh the list information.

      • Click cogwheel in the upper right corner of the list to customize the information displayed in the list.

    Receive the latest news, articles and updates from KubeSphere


    Thanks for the feedback. If you have a specific question about how to use KubeSphere, ask it on Slack. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.

    Previous : Delete PVCs
    What’s on this Page