Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ Cloud Container Engine/ User Guide/ Storage/ DSS/ Using DSS Through a Static PV

Using DSS Through a Static PV

Updated on 2025-02-18 GMT+08:00

CCE allows you to create a PV using an existing DSS disk. After the PV is created, you can create a PVC and bind it to the PV. This mode applies to scenarios where underlying storage is available.

Prerequisites

  • You have created a DSS disk that meets the following requirements:
    • The DSS disk cannot be a system disk or shared disk.
    • The DSS disk must be of the SCSI type (the default disk type is VBD when you create a DSS disk).
    • The DSS disk must be available and not used by other resources.
    • If the DSS disk is encrypted, the key must be available.
    • The DSS disk must be in the default enterprise project or the enterprise project to which the cluster belongs.

Notes and Constraints

  • DSS disks cannot be attached across AZs and cannot be used by multiple workloads, multiple pods of the same workload, or multiple tasks. Data sharing of a shared disk is not supported between nodes in a CCE cluster. If a DSS disk is attached to multiple nodes, I/O conflicts and data cache conflicts may occur. Therefore, select only one pod when creating a Deployment that uses DSS.
  • If an HPA policy is used to expand the capacity of a workload with a DSS disk attached, new pods cannot be started because the DSS disk cannot attach to them.

Using an Existing DSS Disk on the Console

  1. Log in to the CCE console and click the cluster name to access the cluster console.
  2. Statically create a PVC and PV.

    1. Choose Storage in the navigation pane. In the right pane, click the PVCs tab. Click Create PVC in the upper right corner. In the dialog box displayed, configure PVC parameters.

      Parameter

      Description

      PVC Type

      In this example, select DSS.

      PVC Name

      Enter the PVC name, which must be unique in a namespace.

      Creation Method

      • If underlying storage is available, create a PV or use an existing PV to statically create a PVC.
      • If no underlying storage is available, select Dynamically provision. For details, see Using DSS Through a Dynamic PV.

      In this example, select Create new to create both a PV and PVC on the console.

      PVa

      Select an existing PV in the cluster. For details about how to create a PV, see "Creating a storage volume" in Related Operations.

      You do not need to specify this parameter in this example.

      DSSb

      Click Select DSS. On the displayed page, select the DSS volume that meets your requirements and click OK.

      PV Nameb

      Enter the PV name, which must be unique in the same cluster.

      Access Modeb

      DSS volumes support only ReadWriteOnce, indicating that a storage volume can be mounted to one node in read/write mode. For details, see Volume Access Modes.

      Reclaim Policyb

      You can select Delete or Retain to specify the reclaim policy of the underlying storage when the PVC is deleted. For details, see PV Reclaim Policy.

      NOTE:

      a: The parameter is available when Creation Method is set to Use existing.

      b: The parameter is available when Creation Method is set to Create new.

    2. Click Create to create a PVC and a PV.

      You can choose Storage in the navigation pane and view the created PVC and PV on the PVCs and PVs tab pages, respectively.

  3. Create an application.

    1. Choose Workloads in the navigation pane. In the right pane, click the StatefulSets tab.
    2. Click Create Workload in the upper right corner. On the displayed page, click Data Storage in the Container Settings area and click Add Volume to select PVC.
      Mount and use storage volumes, as shown in Table 1. For details about other parameters, see Workloads.
      Table 1 Mounting a storage volume

      Parameter

      Description

      PVC

      Select an existing DSS volume.

      A DSS volume can be mounted to only one workload.

      Mount Path

      Enter a mount path, for example, /tmp.

      This parameter specifies a container path to which a data volume will be mounted. Do not mount the volume to a system directory such as / or /var/run. This may lead to container errors. Mount the volume to an empty directory. If the directory is not empty, ensure that there are no files that affect container startup. Otherwise, the files will be replaced, leading to container startup failures or workload creation failures.
      NOTICE:

      If a volume is mounted to a high-risk directory, use an account with minimum permissions to start the container. Otherwise, high-risk files on the host may be damaged.

      Subpath

      Enter the subpath of the storage volume and mount a path in the storage volume to the container. In this way, different folders of the same storage volume can be used in a single pod. tmp, for example, indicates that data in the mount path of the container is stored in the tmp folder of the storage volume. If this parameter is left blank, the root path will be used by default.

      Permission

      • Read-only: You can only read the data in the mounted volumes.
      • Read-write: You can modify the data volumes mounted to the path. Newly written data will not be migrated if the container is migrated, which may cause data loss.

      In this example, the disk is mounted to the /data path of the container. The container data generated in this path is stored in the DSS disk.

      NOTE:

      A non-shared DSS disk can be attached to only one workload pod. If there are multiple pods, extra pods cannot start properly. Ensure that the number of workload pods is 1 if a DSS disk is attached.

      If multiple workload pods are needed, create a StatefulSet and dynamically mount a PV to each pod. For details, see Dynamically Mounting a DSS Disk to a StatefulSet.

    3. After the configuration, click Create Workload.

      After the workload is created, the data in the container mount directory will be persistently stored. Verify the storage by referring to Verifying Data Persistence.

Using an Existing DSS Disk Through kubectl

  1. Use kubectl to access the cluster.
  2. Create a PV. If a PV has been created in your cluster, skip this step.

    1. Create the pv-dss.yaml file.
      apiVersion: v1
      kind: PersistentVolume
      metadata:
        annotations:
          pv.kubernetes.io/provisioned-by: everest-csi-provisioner
          everest.io/reclaim-policy: retain-volume-only         # (Optional) The underlying volume is retained when the PV is deleted.
        name: pv-dss    # PV name
        labels:
          failure-domain.beta.kubernetes.io/region: <your_region>   # Region of the node where the application is to be deployed
          failure-domain.beta.kubernetes.io/zone: <your_zone>       # AZ of the node where the application is to be deployed
      spec:
        accessModes:
          - ReadWriteOnce     # Access mode, which must be ReadWriteOnce for DSS
        capacity:
          storage: 10Gi       # Disk capacity, in the unit of GiB. The value ranges from 1 to 32768.
        csi:
          driver: disk.csi.everest.io     # Dependent storage driver for the mounting
          fsType: ext4    # Must be the same as that of the original file system of the disk.
          volumeAttributes:
            everest.io/disk-mode: SCSI           # Device type of the DSS disk. Only SCSI is supported.
            everest.io/disk-volume-type: SAS     # Disk type
            everest.io/csi.dedicated-storage-id: <dss_id>     # ID of the DSS storage pool
            storage.kubernetes.io/csiProvisionerIdentity: everest-csi-provisioner
            everest.io/crypt-key-id: <your_key_id>    # (Optional) Encryption key ID. Mandatory for an encrypted disk.
            everest.io/enterprise-project-id: <your_project_id>  # (Optional) Enterprise project ID. If an enterprise project is specified, use the same enterprise project when creating a PVC. Otherwise, the PVC cannot be bound to a PV.
        persistentVolumeReclaimPolicy: Delete    # Reclaim policy
        storageClassName: csi-disk-dss              # Storage class name of the DSS disk
      Table 2 Key parameters

      Parameter

      Mandatory

      Description

      everest.io/reclaim-policy: retain-volume-only

      No

      Optional.

      Only retain-volume-only is supported.

      This parameter is valid only when the Everest version is 1.2.9 or later and the reclaim policy is Delete. If the reclaim policy is Delete and the current value is retain-volume-only, the associated PV is deleted while the underlying storage volume is retained, when a PVC is deleted.

      failure-domain.beta.kubernetes.io/region

      Yes

      Region where the cluster is located.

      For details about its value, see Regions and Endpoints.

      failure-domain.beta.kubernetes.io/zone

      Yes

      AZ where the DSS volume is created. It must be the same as the AZ planned for the workload.

      For details about its value, see Regions and Endpoints.

      fsType

      Yes

      File system type, which defaults to ext4.

      everest.io/disk-volume-type

      Yes

      Disk type. All letters are in uppercase.
      • SAS: high I/O
      • SSD: ultra-high I/O

      everest.io/csi.dedicated-storage-id

      Yes

      ID of the DSS storage pool where the DSS disk resides.

      To obtain a DSS storage pool ID, log in to the Cloud Server Console. In the navigation pane, choose Dedicated Distributed Storage Service > Storage Pools and click the name of the target storage pool. On the resource pool details page, copy the pool ID.

      everest.io/crypt-key-id

      No

      Mandatory when the disk is encrypted. Enter the encryption key ID selected during disk creation.

      To obtain an encryption key ID, log in to the Cloud Server Console. In the navigation pane, choose Dedicated Distributed Storage Service > Disks. Click the name of the target disk to go to its details page. On the Summary tab page, copy the value of KMS Key ID in the Configuration Information area.

      everest.io/enterprise-project-id

      No

      Optional.

      Enterprise project ID of DSS. If an enterprise project is specified, use the same enterprise project when creating a PVC. Otherwise, the PVC cannot be bound to a PV.

      To obtain an enterprise project ID, log in to the Cloud Server Console. In the navigation pane, choose Dedicated Distributed Storage Service > Disks. Click the name of the target disk to go to its details page. On the Summary tab page, click the enterprise project in Management Information to access the enterprise project console. Copy the corresponding ID to obtain the ID of the enterprise project to which the DSS disk belongs.

      persistentVolumeReclaimPolicy

      Yes

      The Delete and Retain reclaim policies are supported. For details, see PV Reclaim Policy. If high data security is required, select Retain to prevent data from being deleted by mistake.

      Delete:

      • If everest.io/reclaim-policy is not specified, both the PV and DSS disk will be deleted when a PVC is deleted.
      • If everest.io/reclaim-policy is set to retain-volume-only, when a PVC is deleted, the PV will be deleted but the DSS disk will be retained.

      Retain: When a PVC is deleted, both the PV and underlying storage resources will be retained. You need to manually delete these resources. After the PVC is deleted, the PV is in the Released state and cannot be bound to a PVC again.

      storageClassName

      Yes

      The StorageClass for DSS disks is csi-disk-dss.

    2. Run the following command to create a PV:
      kubectl apply -f pv-dss.yaml

  3. Create a PVC.

    1. Create the pvc-dss.yaml file.
      apiVersion: v1
      kind: PersistentVolumeClaim
      metadata:
        name: pvc-dss
        namespace: default
        annotations:
          everest.io/disk-volume-type: SAS    # Disk type
          everest.io/csi.dedicated-storage-id: <dss_id>     # ID of the DSS storage pool
          everest.io/crypt-key-id: <your_key_id>    # (Optional) Encryption key ID. Mandatory for an encrypted disk.
          everest.io/enterprise-project-id: <your_project_id>  # (Optional) Enterprise project ID. If an enterprise project is specified, use the same enterprise project when creating a PVC. Otherwise, the PVC cannot be bound to a PV.
        labels:
          failure-domain.beta.kubernetes.io/region: <your_region>   # Region of the node where the application is to be deployed
          failure-domain.beta.kubernetes.io/zone: <your_zone>       # AZ of the node where the application is to be deployed
      spec:
        accessModes:
        - ReadWriteOnce               # The value must be ReadWriteOnce for DSS.
        resources:
          requests:
            storage: 10Gi             # Disk capacity, ranging from 1 to 32768. The value must be the same as the storage size of the existing PV.
        storageClassName: csi-disk-dss    # The StorageClass is DSS.
        volumeName: pv-dss            # PV name
      Table 3 Key parameters

      Parameter

      Mandatory

      Description

      failure-domain.beta.kubernetes.io/region

      Yes

      Region where the cluster is located.

      For details about its value, see Regions and Endpoints.

      failure-domain.beta.kubernetes.io/zone

      Yes

      AZ where the disk is created. It must be the same as the AZ planned for the workload.

      For details about its value, see Regions and Endpoints.

      everest.io/csi.dedicated-storage-id

      Yes

      ID of the DSS storage pool where the DSS disk resides.

      To obtain a DSS storage pool ID, log in to the Cloud Server Console. In the navigation pane, choose Dedicated Distributed Storage Service > Storage Pools and click the name of the target storage pool. On the resource pool details page, copy the pool ID.

      storage

      Yes

      Requested capacity in the PVC, in Gi.

      The value must be the same as the storage size of the existing PV.

      volumeName

      Yes

      PV name, which must be the same as the PV name in 1.

      storageClassName

      Yes

      StorageClass name, which must be the same as the StorageClass of the PV in 1.

      The StorageClass for DSS disks is csi-disk-dss.

    2. Run the following command to create a PVC:
      kubectl apply -f pvc-dss.yaml

  4. Create an application.

    1. Create a file named web-dss.yaml. In this example, the disk is mounted to the /data path.
      apiVersion: apps/v1
      kind: StatefulSet
      metadata:
        name: web-dss
        namespace: default
      spec:
        replicas: 1
        selector:
          matchLabels:
            app: web-dss
        serviceName: web-dss   # Headless Service name
        template:
          metadata:
            labels:
              app: web-dss
          spec:
            containers:
            - name: container-1
              image: nginx:latest
              volumeMounts:
              - name: pvc-disk-dss    # Volume name, which must be the same as the volume name in the volumes field
                mountPath: /data  # Location where the storage volume is mounted
            imagePullSecrets:
              - name: default-secret
            volumes:
              - name: pvc-disk-dss    # Volume name, which can be customized
                persistentVolumeClaim:
                  claimName: pvc-dss    # Name of the created PVC
      ---
      apiVersion: v1
      kind: Service
      metadata:
        name: web-dss   # Headless Service name
        namespace: default
        labels:
          app: web-dss
      spec:
        selector:
          app: web-dss
        clusterIP: None
        ports:
          - name: web-dss
            targetPort: 80
            nodePort: 0
            port: 80
            protocol: TCP
        type: ClusterIP
    2. Run the following command to create a workload to which the DSS volume is mounted:
      kubectl apply -f web-dss.yaml

      After the workload is created, the data in the container mount directory will be persistently stored. Verify the storage by referring to Verifying Data Persistence.

Verifying Data Persistence

  1. View the deployed application and DSS volume files.

    1. Run the following command to view the created pod:
      kubectl get pod | grep web-dss
      Expected output:
      web-dss-0                  1/1     Running   0               38s
    2. Run the following command to check whether the DSS volume has been mounted to the /data path:
      kubectl exec web-dss-0 -- df | grep data

      Expected output:

      /dev/sdc              10255636     36888  10202364   0% /data
    3. Run the following command to check the files in the /data path:
      kubectl exec web-dss-0 -- ls /data

      Expected output:

      lost+found

  2. Run the following command to create a file named static in the /data path:

    kubectl exec web-dss-0 --  touch /data/static

  3. Run the following command to check the files in the /data path:

    kubectl exec web-dss-0 -- ls /data

    Expected output:

    lost+found
    static

  4. Run the following command to delete the pod named web-dss-0:

    kubectl delete pod web-dss-0

    Expected output:

    pod "web-dss-0" deleted

  5. After the deletion, the StatefulSet controller automatically creates a replica with the same name. Run the following command to check whether the files in the /data path have been modified:

    kubectl exec web-dss-0 -- ls /data

    Expected output:

    lost+found
    static

    The static file is retained, indicating that the data in the DSS volume can be stored persistently.

Related Operations

You can also perform the operations listed in Table 4.
Table 4 Related operations

Operation

Description

Procedure

Creating a storage volume (PV)

Create a PV on the CCE console.

  1. Choose Storage in the navigation pane. In the right pane, click the PVs tab. Click Create PersistentVolume in the upper right corner. In the dialog box displayed, configure parameters.
    • Volume Type: Select DSS.
    • DSS: Click Select DSS. On the displayed page, select the disk that meets your requirements and click OK.
    • PV Name: Enter the PV name, which must be unique in a cluster.
    • Access Mode: DSS volumes support only ReadWriteOnce, indicating that a storage volume can be mounted to one node in read/write mode. For details, see Volume Access Modes.
    • Reclaim Policy: Delete or Retain is supported. For details, see PV Reclaim Policy.
  2. Click Create.

Expanding the capacity of DSS storage

Quickly expand the capacity of an attached DSS disk on the CCE console.

  1. Choose Storage in the navigation pane. In the right pane, click the PVCs tab. Click More in the Operation column of the target PVC and select Scale-out.
  2. Enter the capacity to be added and click OK.

Viewing events

View event names, event types, number of occurrences, Kubernetes events, first occurrence time, and last occurrence time of the PVC or PV.

  1. Choose Storage in the navigation pane. In the right pane, click the PVCs or PVs tab.
  2. Click View Events in the Operation column of the target PVC or PV to view events generated within one hour (events are retained for one hour).

Viewing a YAML file

View, copy, or download the YAML file of a PVC or PV.

  1. Choose Storage in the navigation pane. In the right pane, click the PVCs or PVs tab.
  2. Click View YAML in the Operation column of the target PVC or PV to view or download the YAML.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback