Available StorageClasses
NETWAYS Managed Kubernetes clusters are provided with several predefined StorageClasses.
If none of them meet your requirements, you can create your own StorageClasses.
Further information can be found in the Cinder CSI Driver documentation.
Alternatively, you can contact one of our MyEngineers® at any time.
~ : kubectl get sc
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION
standard (default) cinder.csi.openstack.org Delete Immediate true
general-purpose-1 cinder.csi.openstack.org Delete Immediate true
general-purpose-1-encrypted cinder.csi.openstack.org Delete Immediate true
general-purpose-2 cinder.csi.openstack.org Delete Immediate true
general-purpose-2-encrypted cinder.csi.openstack.org Delete Immediate true
performance-optimized-1 cinder.csi.openstack.org Delete Immediate true
performance-optimized-1-encrypted cinder.csi.openstack.org Delete Immediate true
performance-optimized-2 cinder.csi.openstack.org Delete Immediate true
performance-optimized-2-encrypted cinder.csi.openstack.org Delete Immediate true
standard
standard is the default StorageClass in NETWAYS Managed Kubernetes clusters.
It provisions an ext4‑formatted volume in OpenStack that is deleted as soon as the associated PersistentVolumeClaim (PVC) is removed.
Volume expansion is also supported, allowing the size of a PVC to be adjusted later, with Kubernetes handling the resizing.
The IOPS limit is 1000 IOPS, with a short‑term boost up to 2000 IOPS for 60 seconds. If you wish to use a different StorageClass as the default, the default class annotation must be removed. However, the StorageClass must not be deleted, as it would otherwise be recreated during a cluster upgrade. Unlike all other StorageClasses, any changes to this one will be ignored.
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
storageclass.kubernetes.io/is-default-class: "true"
name: standard
allowVolumeExpansion: true
parameters:
csi.storage.k8s.io/fstype: ext4
provisioner: cinder.csi.openstack.org
reclaimPolicy: Delete
volumeBindingMode: Immediate
Other StorageClasses
The other StorageClasses also all use the EXT4 file system. The information about IOPS and encryption is located as an annotation on the respective StorageClass and can therefore be retrieved directly from the cluster.
For example, this is how it looks like in the cluster:
---
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
kubernetes.io/description: |-
Base IOPS: ~2000 IOPS
Burst IOPS: Up to 4000 IOPS
Burst Duration: 60 seconds
Encrypted: False
name: general-purpose-2
allowVolumeExpansion: true
parameters:
csi.storage.k8s.io/fstype: ext4
type: general-purpose-2
provisioner: cinder.csi.openstack.org
reclaimPolicy: Delete
volumeBindingMode: Immediate
---
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
kubernetes.io/description: |-
Base IOPS: ~2500 IOPS
Burst IOPS: Up to 5000 IOPS
Burst Duration: 60 seconds
Encrypted: True
name: performance-optimized-1-encrypted
allowVolumeExpansion: true
parameters:
csi.storage.k8s.io/fstype: ext4
type: performance-optimized-1-encrypted
provisioner: cinder.csi.openstack.org
reclaimPolicy: Delete
volumeBindingMode: Immediate
Legacy StorageClasses
If the StorageClasses mentioned above are not present in the cluster, a cluster upgrade must be performed. During this process, the new StorageClasses will be added. The old ones will remain.
Support for ReadWriteMany (RWX)
Currently, no volumes with the RWX access mode are provided.
This feature is on our roadmap, but we cannot give a precise timeframe at the moment.
In the meantime, you can implement your own solution, for example based on NFS or Rook Ceph. Our MyEngineers® are happy to help you with that.