Configure your PVs Autoscaling workload
- 1 Minute to read
- Print
- PDF
Configure your PVs Autoscaling workload
- 1 Minute to read
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
This section describes how to configure your workload in PVs Autoscaling.
To configure workloads, edit the workload YAML file.
Configure the storage class
To initiate your workload Pods for PVs Autoscaling, you need to configure the storage class.
You can use the default, Zesty Disk storage class or define a custom storage class. To change from a previously-defined Zesty Disk storage class, follow the instructions for a custom storage class.
Configure the default, Zesty Disk storage class
To use the Zesty Disk class, change the storage class setting to zesty-sc.
Also, for increased utilization, consider changing the initial PVC size.
Example:
....
volumeClaimTemplates:
- metadata:
name: democlaim
spec:
accessModes: [ "ReadWriteOnce" ]
storageClassName: "zesty-sc"
resources:
requests:
storage: 25Gi
...Configure a custom storage class
To use a custom class, or to change from the storage class that was set during installation, use an annotation with the name of the custom storage class.
You should also remove the default text: storageClassName: "zesty-sc"
Example:
....
volumeClaimTemplates:
- metadata:
name: democlaim
annotations:
disk.zesty.co/storageClassName: "io1-sc"
spec:
accessModes: [ "ReadWriteOnce" ]
....Configure workload policy
Once the Zesty Disk storage class is configured, you can set policies to control how PVs Autoscaling will work. The current supported policies are:
Set the minimum Zesty Disk size, using “requests: storage”
Set the maximum Zesty Disk size, using “limits: storage”
Set the Zesty Disk minimum buffer size, using “requests: buffer”
Example:
....
volumeClaimTemplates:
- metadata:
name: democlaim
spec:
accessModes: [ "ReadWriteOnce" ]
storageClassName: "zesty-sc"
resources:
requests:
storage: 10Gi
buffer: 40Gi
limits:
storage: 500Gi
...Was this article helpful?