Closed tipruzs closed 5 years ago
I need it as well! Please implement!
I just want to know why do you prefer one fstype from the others?
There are a many applications which profit from xfs for performance reasons, e.g. mongodb
This is already possible. You can create a new (custom) storage class with a parameter fsType
:
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
namespace: kube-system
name: hcloud-volumes-xfs
annotations:
storageclass.kubernetes.io/is-default-class: "true"
provisioner: csi.hetzner.cloud
volumeBindingMode: WaitForFirstConsumer
parameters:
fsType: xfs
And use this storage class in your pvc:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: csi-pvc
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: hcloud-volumes-xfs
Can I also set the location of the storage?
A volume will be created in the location of the node. You can only attach a volume to a node in the same location.
I couldn't deploy to multiple locations.. Do you maybe have an example for multi location deployment?
@deacix you can not create a multi-location deployment, because volumes can only be accessed within the location of the node.
But other cloud provider can handle it, why not Hetzner?
Is it possible to implement fstype parameter, so we can choose the filesystem (xfs/ext4) during provisioning?