ChenYi015 commented on PR #2650:
URL: https://github.com/apache/celeborn/pull/2650#issuecomment-2275804290
If we want to use `volumeClaimTemplates`, suppose `ssd-storage-class` is a
valid storage class in your Kubernetes cluster that provided by a cloud
provider or defined by yourself that can be used to provide SSD cloud disks
dynamically, the configuratio will be like as follows:
```yaml
master:
volumeClaimTemplates:
- metadata:
name: celeborn-ratis
celeborn.apache.org/disk-type: SSD
celeborn.apache.org/disk-capacity: 100Gi
spec:
accessModes:
- ReadWriteOnce
resources:
request:
storage: 100Gi
limits:
storage: 100Gi
storageClassName: ssd-storage-class
volumeMounts:
- name: celeborn-ratis
mountPath: /mnt/celeborn_ratis
worker:
volumeClaimTemplates:
- metadata:
name: disk1
annotations:
celeborn.apache.org/disk-type: SSD
celeborn.apache.org/disk-capacity: 100Gi
spec:
accessModes:
- ReadWriteOnce
resources:
request:
storage: 100Gi
limits:
storage: 100Gi
storageClassName: ssd-storage-class
volumeMounts:
- name: disk1
mountPath: /mnt/disk1
```
The annotations `celeborn.apache.org/disk-type` and
`celeborn.apache.org/disk-capacity` are used by Helm to render
`celeborn.worker.storage.dirs` in configmap.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
