Expanding the Ephemeral Storage Capacity
Scenarios
By default, CCI allocates 30 GiB of free ephemeral storage space to a pod. The storage space is unavailable when the pod is not in use. If the CCE Cloud Bursting Engine for CCI add-on is used to schedule the workloads to CCI and the pod needs to write a large amount of data to rootfs or emptyDir or the image size is greater than 30 GiB, you can expand the ephemeral storage space.
Precautions
- The maximum ephemeral storage capacity is 994 GiB.
- When the ephemeral storage space is expanded, workload creation is slower than before because the capacity expansion takes time.
- If the CCE Cloud Bursting Engine for CCI add-on is used, you must add resource.cce.io/extra-ephemeral-storage-in-GiB to the pod annotation to expand the capacity.
Expanding the Ephemeral Storage Using YAML
- Add 10-GiB ephemeral storage space when creating a Deployment. The YAML file is defined as follows:
apiVersion: apps/v1 kind: Deployment metadata: name: nginx namespace: ns labels: bursting.cci.io/burst-to-cci: enforce # Forcibly schedules the pod to CCI 2.0. spec: replicas: 1 selector: matchLabels: app: nginx template: metadata: labels: app: nginx annotations: resource.cce.io/extra-ephemeral-storage-in-GiB: "10" # Ephemeral storage capacity to be added, in GiB spec: containers: - image: nginx:alpine name: container-0 resources: limits: cpu: 250m memory: 512Mi requests: cpu: 250m memory: 512Mi imagePullSecrets: - name: default-secret - Add 10-GiB ephemeral storage space when creating a pod. The YAML file is defined as follows:
apiVersion: v1 kind: Pod metadata: name: nginx namespace: ns labels: bursting.cci.io/burst-to-cci: enforce annotations: resource.cce.io/extra-ephemeral-storage-in-GiB: "10" # Ephemeral storage capacity to be added, in GiB spec: containers: - image: nginx:alpine name: container-0 resources: limits: cpu: 250m memory: 512Mi requests: cpu: 250m memory: 512Mi imagePullSecrets: - name: default-secret
Verifying the Capacity Expansion
- Log in to the CCE console.
- Click the name of the target CCE cluster to go to the cluster Overview page.
- In the navigation pane, choose Workloads. Then click the Pods tab.
- Locate the target pod and choose More > Remote Login.
- Enter lsblk and press Enter to verify that the system disk size is 40 GiB after the expansion. (The ephemeral storage capacity is 30 GiB by default.)

Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot