issues with custom storage classes? any idea?

[Gilaco]

Hey,
I wondered if any of you tried to create custom StorageClass.

seems that when I tried to create my own class - it fails to provision the volumes;
might be that I need to specify anything inside the kube.tf config?

this is the class that I tried to create...
(when I refer my pvc to the default class created with the cluster if it provisioned ok... only custom not working)

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: aerospike-sc
  labels:
    app: aerospike
provisioner: csi.hetzner.cloud
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: true
reclaimPolicy: Delete
parameters:
  csi.storage.k8s.io/node-publish-secret-namespace: kube-system

really appreciate your help
thanks
G

[mysticaltech]

@ifeulner @WolfspiritM Any ideas here?

@Gilaco I do not think it's related to the Kube.tf. What do you use, volumes or node storage?

[Gilaco]

Basically I want to use both for different cases.

But - in this case I want to create a simple custom class it can be using node-storage (I assume it's faster ssd)
I want to use this specific class for specific component (Aerospike db). Once I succeed with the simple case I plan to annotate different classes for different storage types or node affinity

• The default longhorn class that is created when I enable longhorn works ok... cloning it on a different class name didn't.

• cloning the default hz volumes class (hcloud) didn't work for me when I enabled longhorn... and also the longhorn volume size on the example agent pool - when I uncomment it and give a value (like 100) throws an error on terraform

I assume that perhaps I stressed too much the kube configuration that perhaps raised some cross collisions with something

Would love an explanation how to use it right. I want to combine longhorn with volumes and decide per service how and when to use what...

Thanks
G

[mysticaltech]

@Gilaco I understand! This is actually brand new territory for all of us, we just deploy longhorn the best we can (community members submitted PRs for that), and then the config is up to users. If you can help us figure out how to configure longhorn well with classes, and even later submit a PR to add some additional docs, it would be great!

I believe that this is more to do with longhorn than kube-hetzner, so definitely the longhorn docs, and forums would be a great place to search / ask questions. Same as its slack channel.

[Gilaco]

Sure, on it 😁

Cheers
G

[ifeulner]

@Gilaco @mysticaltech I am currently collecting some best practices for using longhorn on hcloud, still work in progress but maybe it helps - see my gist https://gist.github.com/ifeulner/d311b2868f6c00e649f33a72166c2e5b

[mysticaltech]

This is the guide on how to use Longhorn, including storage classes and more by @ifeulner https://gist.github.com/ifeulner/d311b2868f6c00e649f33a72166c2e5b