Tutorial
StorageClasses
SuperMap iManager supports to add StorageClasses for services and applications data storing. A StorageClass provides a way for administrators to describe different available storage types. StorageClasses can map to quality-of-service levels, backup policies, or to arbitrary policies determined by cluster administrators. Each StorageClass contains the fields provisioner, parameters, and reclaimPolicy, which are used when a Persistent Volume belonging to the class needs to be dynamically provisioned. Users can request a particular class using the name of a StorageClass object. More details please refer to Kubernetes Documentation.
If you already have a StorageClass, configure the parameter ‘deploy_storage_class_name’ in values.yaml file(please refer to Guides > Deployment Guide > Install iManager), or add the name of StorageClass through iManager UI.
Add StorageClasses
- Clicks Storage > StorageClasses on the left navigation bar of iManager.
- Clicks on Add StorageClasses.
-
Fills in the name of StorageClass.
- StorageClass Name: The name of StorageClass in the YAML file.
Manage StorageClasses
On the StorageClasses page, users can delete existing StorageClasses, and bind/unbind basic services and applications to the specified StorageClass.