Container Compute Service:Use a dynamic disk as a persistent volume

Connect to your ACS cluster. For more information, see Obtain the kubeconfig file of a cluster and use kubectl to connect to the cluster and Use kubectl on Cloud Shell to manage ACS clusters.

Modify and save the following YAML as disk-sc.yaml based on the parameters described in the table below.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: alicloud-disk-essd
provisioner: diskplugin.csi.alibabacloud.com
parameters:
  type: cloud_essd
  fstype: ext4
  performanceLevel: PL1
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: true

The following table describes the parameters.

Create a StorageClass.

kubectl create -f disk-sc.yaml

Check the StorageClass.

kubectl get sc

Expected output:

NAME                             PROVISIONER                       RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
alicloud-disk-essd               diskplugin.csi.alibabacloud.com   Delete          WaitForFirstConsumer   true                   78s
alicloud-disk-topology-alltype   diskplugin.csi.alibabacloud.com   Delete          WaitForFirstConsumer   true                   23d
......

Save the following YAML as disk-pvc.yaml.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: disk-pvc
spec:
  accessModes:
  - ReadWriteOncePod
  volumeMode: Filesystem
  resources:
    requests:
      storage: 20Gi
  storageClassName: alicloud-disk-essd

The following table describes the parameters.

Create the PVC.

kubectl create -f disk-pvc.yaml

Check the PVC.

kubectl get pvc

The expected output shows that the PVC has not yet been bound to a PV because volumeBindingMode is set to WaitForFirstConsumer.

NAME       STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS         VOLUMEATTRIBUTESCLASS   AGE
disk-pvc   Pending                                      alicloud-disk-essd   <unset>                 7s

Save the following YAML as disk-test.yaml.

The following YAML defines a StatefulSet with one Pod. The Pod requests storage resources through a PVC named disk-pvc and mounts the volume to the /data path.

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: disk-test
spec:
  replicas: 1
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: registry.cn-hangzhou.aliyuncs.com/acs-sample/nginx:latest
        ports:
        - containerPort: 80
        volumeMounts:
        - name: pvc-disk
          mountPath: /data
      volumes:
        - name: pvc-disk
          persistentVolumeClaim:
            claimName: disk-pvc

Create the StatefulSet and mount the disk.

kubectl create -f disk-test.yaml

Check the deployment status of the Pod in the StatefulSet.

kubectl get pod | grep disk-test

The output shows one Pod, as expected, because replicas is set to 1 in the StatefulSet.

disk-test-0   1/1     Running   0          52s

Check the PVC.

kubectl get pvc

The expected output shows that the PVC is now bound to the automatically created PV of the disk type.

NAME       STATUS   VOLUME                   CAPACITY   ACCESS MODES   STORAGECLASS         VOLUMEATTRIBUTESCLASS   AGE
disk-pvc   Bound    d-uf698s3h14isyj6b****   20Gi       RWOP           alicloud-disk-essd   <unset>                 111s

Check the mount path to confirm that the disk is mounted.

kubectl exec disk-test-0 -- df | grep data

Expected output:

/dev/vdb        20466256      24  20449848   1% /data

Log on to the ACS console.

On the Clusters, click the name of the cluster to go to the cluster management page.

In the left-side navigation pane of the cluster management page, choose Volumes > StorageClasses.

Create a StorageClass.

1. On the StorageClasses page, click Create.

2. In the dialog box that appears, configure the parameters and then click Create.

   Parameter	Description	Example
   Name	The name of the StorageClass. Follow the format requirements on the screen.	alicloud-disk-essd
   PV Type	Select Cloud Disk.	Cloud Disk
   Parameter	The default parameter is type, which specifies the disk type. Valid values are: cloud_essd_entry: ESSD Entry disk cloud_auto: ESSD AutoPL disk cloud_essd (default): ESSD cloud_ssd: standard SSD cloud_efficiency: ultra disk You can combine these parameters, for example, type: cloud_efficiency, cloud_ssd, cloud_essd. The system will try to create a disk of each specified type in order until one is created. Note Choose a disk type based on your billing and performance needs. For more information, see Prices of block storage devices and Block storage performance. You can add the following parameters: fstype The file system type for the disk. The default is ext4. Supported types are ext3, ext4, and xfs. performanceLevel The performance level of the ESSD. The default is PL1. Supported levels are PL0, PL1, PL2, and PL3. For more information, see ESSDs.	type:cloud_essd
   Reclaim Policy	The reclaim policy for the disk. Only Delete is supported, meaning that when you delete the PVC, the system also deletes the PV and its underlying disk.	Delete
   Binding Mode	The volume binding mode. If you are using a multi-zone cluster, we recommend setting this to WaitForFirstConsumer. Delays volume binding. The Pod is scheduled first, and then the disk is created based on the Pod's Availability Zone. Immediate: The disk is created before the Pod. Important If you use ACS computing power in an ACK cluster and the ACS Pod needs to mount a disk, use nodeSelector or ResourcePolicy to schedule the Pod to a virtual node. If you schedule the Pod by adding the Pod label alibabacloud.com/acs: "true", StorageClasses with volumeBindingMode: WaitForFirstConsumer are not supported.	WaitForFirstConsumer

In the left-side navigation pane of the cluster management page, choose Volumes > Persistent Volume Claims.

On the Persistent Volume Claims page, click Create.

In the dialog box that appears, configure the parameters and then click Create.

After the PVC is created, you can see it on the Persistent Volume Claims page. Because the binding mode in the StorageClass is WaitForFirstConsumer, the PVC is not yet bound to a PV and its status is Pending.

In the left-side navigation pane of the cluster management page, choose Workloads > StatefulSets.

On the StatefulSets page, click Create from Image.

Configure the parameters for the StatefulSet, then click Create.

Configure the following parameters and keep the default values for the others. For more information, see Use a StatefulSet to create a stateful application.

Check the application deployment status.

1. On the StatefulSets page, click the name of the application.

2. On the Pods tab, confirm that the Pod is running properly (its status is Running).

Check the PV and PVC.

• On the Persistent Volumes page, you can see that a PV has been automatically created. The name of the PV corresponds to the disk ID.

• On the Persistent Volume Claims page, you can see that the PVC is now bound to the PV, and its status is Bound.