< 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. Extension User Guide / 
  4. Application Management for Cluster Federation / 
  5. Persistent Volume Claims / 
  6. View Persistent Volume Claim List

Documentation

Last updated:
    Edit

    View Persistent Volume Claim List

    This section explains how to view the list of Persistent Volume Claims.

    Prerequisites

    • Application Management for Cluster Federation should have been installed and enabled.

    • You should join a multi-cluster project and have the Federated Project Viewing permission within the project.

    Steps

    1. Log in to the KubeSphere web console with a user who has the Federated Project Viewing permission, and access your multi-cluster project.

    2. Click Persistent Volume Claim in the left navigation pane.

      • The Persistent Volume Claim list provides the following information:

        Parameter Description

        Name

        The name, alias, and storage class of the Persistent Volume Claim.

        Status

        Current status of the Persistent Volume Claim:

        • Bound: The system has created a Persistent Volume based on the Persistent Volume Claim, and the Persistent Volume Claim is bound to the Persistent Volume.

        • Pending: The system has created the Persistent Volume Claim, but the corresponding Persistent Volume has not been created yet.

        • Updating: The settings of the Persistent Volume Claim have changed, and the system is updating the Persistent Volume Claim.

        • Deleting: The system is deleting the Persistent Volume Claim.

        • Lost: The system has bound the Persistent Volume Claim to a Persistent Volume, but the corresponding Persistent Volume cannot be found. In this state, the Persistent Volume may have been deleted.

        Mount Status

        Whether the Persistent Volume associated with the Persistent Volume Claim is already mounted to a container.

        Access Mode

        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.

        Creation Time

        The creation time of the Persistent Volume Claim.

      • Click the search box at the top of the list to search for Persistent Volume Claims 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 : Create Persistent Volume Claims
    What’s on this Page