Container Service for Kubernetes:Change the disk category

Prerequisites

Before you begin, ensure that you have:

• A cluster running Kubernetes 1.20 or later with the Container Storage Interface (CSI) plug-in installed. To upgrade your cluster, see Manually upgrade a cluster.

• storage-operator version 1.26.1-50a1499-aliyun or later installed. By default, storage-operator is installed in the cluster. To verify the version, go to the cluster details page in the ACK console, choose Operations > Add-ons in the left-side navigation pane, and click the Storage tab. For more information, see Manage the storage-operator component.

• (ACK dedicated clusters only) Worker and master RAM (Resource Access Management) roles with permission to call the ModifyDiskSpec operation. This is not required for ACK managed clusters. See Create a custom policy.

  Click to view policy content

  {
      "Version": "1",
      "Statement": [
          {
              "Effect": "Allow",
              "Action": [
                  "ecs:CreateSnapshot",
                  "ecs:DescribeSnapshot",
                  "ecs:DeleteSnapshot",
                  "ecs:ModifyDiskSpec",
                  "ecs:DescribeTaskAttribute"
              ],
              "Resource": "*"
          }
      ]
  }

Limitations

• Basic disks and ephemeral disks cannot be changed to other disk categories.

• ESSD AutoPL disks cannot be changed to other disk categories.

• Only pay-as-you-go disks can be mounted as volumes.

• The new disk category must be supported by the ECS instance type of the node hosting your pod. For compatibility details, see Overview of instance families.

• When a category change involves a regional ESSD, the volume's affinity settings cannot be modified. Pods using the disk cannot be rescheduled to other zones.

For a complete list of limits, see Limits.

Supported disk category conversions

The following table summarizes supported upgrades and downgrades.

Usage notes:

• Only ESSD Entry disks can be attached to instances of universal instance families and the e economy instance family.

• The performance level an ESSD can be upgraded to depends on disk capacity. If a higher performance level is unavailable, extend the disk first, then upgrade the performance level.

• After changing a disk to a PL3 ESSD, attach the disk to an instance or restart the instance to activate optimal performance. Data reliability is not affected during this period.

• After the disk category change, billing follows the rules of the new disk category.

• When changing to or from an ESSD AutoPL disk: you can enable or disable performance provision after the change (extra charges apply when enabled — see Modify the provisioned performance of an ESSD AutoPL disk). Performance burst cannot be configured during the change, but can be enabled or disabled after it completes — see Enable or disable performance burst for an ESSD AutoPL disk.

desiredDiskType parameter reference

Use the following values for the desiredDiskType parameter when creating the custom resource in step 2.

Step 1: Enable disk category changes in storage-operator

Run the following command to update the storage-operator ConfigMap and enable the disk category change feature. The feature is implemented by the storage-controller plug-in.

kubectl patch configmap/storage-operator \
  -n kube-system \
  --type merge \
  -p '{"data":{"storage-controller":"{\"imageRep\":\"acs/storage-controller\",\"imageTag\":\"\",\"install\":\"true\",\"template\":\"/acs/templates/storage-controller/install.yaml\",\"type\":\"deployment\"}"}}'

Step 2: Change the disk category

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: nginx-diskspec
spec:
  selector:
    matchLabels:
      app: nginx
  replicas: 1
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: anolis-registry.cn-zhangjiakou.cr.aliyuncs.com/openanolis/nginx:1.14.1-8.6
        ports:
        - containerPort: 80
        volumeMounts:
        - name: pvc-disk
          mountPath: /data
      volumes:
        - name: pvc-disk
          persistentVolumeClaim:
            claimName: disk-pvc
  volumeClaimTemplates:
    - metadata:
        name: pvc-disk
        labels:
          app: nginx
      spec:
        accessModes: [ "ReadWriteOnce" ]
        storageClassName: "alicloud-disk-essd"
        resources:
          requests:
            storage: 40Gi

kubectl create -f StatefulSet.yaml
kubectl get pod -l app=nginx

NAME                 READY   STATUS    RESTARTS   AGE
nginx-diskspec-0     1/1     Running   0          4m4s

kubectl get pvc pvc-disk-nginx-diskspec-0

NAME                           STATUS    VOLUME                   CAPACITY   ACCESS MODES   STORAGECLASS                VOLUMEATTRIBUTESCLASS   AGE
pvc-disk-nginx-diskspec-0      Bound     d-uf6ijdcp3aeoi82w****   40Gi       RWO            alicloud-disk-essd          <unset>                 5m6s

kubectl get pv d-uf6ijdcp3aeoi82w**** -o=jsonpath='{.metadata.labels}'

{"csi.alibabacloud.com/disktype":"cloud_essd.PL1"}

apiVersion: storage.alibabacloud.com/v1beta1
kind: ContainerStorageOperator
metadata:
  name: default
spec:
  operationType: DISKUPGRADE
  operationParams:
    pvNames: "d-uf6ijdcp3aeoi82w****"
    desiredDiskType: "cloud_auto"

kubectl create -f cr.yaml

kubectl get ContainerStorageOperator default -o yaml

  status:
    message: []
    process: 100%
    status: SUCCESS

kubectl get pv d-uf6ijdcp3aeoi82w**** -o=jsonpath='{.metadata.labels}'

{"csi.alibabacloud.com/disktype":"cloud_auto"}

What's next

• Expand a cloud disk

• Manage the storage-operator component