9.3.2. RHOSP Cinder StorageObject object definition
This RHOSP Cinder storage class example demonstrates how to configure volume types for performance optimization, control availability zone placement for high availability, and specify filesystem types for your persistent volumes.
Example Cinder storage class YAML file
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: <storage-class-name>
provisioner: kubernetes.io/cinder
parameters:
type: fast
availability: nova
fsType: ext4
-
metadata.name: Name of the storage class. The persistent volume claim uses this storage class for provisioning the associated persistent volumes. -
parameter.type: Volume type created in Cinder. Default is empty. -
parameters.availability: Availability Zone. If not specified, volumes are generally round-robined across all active zones where theOpenShift Container Platform cluster has a node. -
parameters.fsType: File system that is created on dynamically provisioned volumes. This value is copied to thefsTypefield of dynamically provisioned persistent volumes, and the file system is created when the volume is mounted for the first time. The default value isext4. The following is a RHOSP Cinder example storage class object definition.