Sample Config Explaination

[ProjectInitiative]

I have read through some of the issues/discussion and know some documentation changes are in the works. I wanted to inquire about the volumeServerDiskCount setting in the provided sample and see if this was like a physical disk count or something different. I seen the enhancement in issue 40 for more granular control over the volume server deployment and I am also run an onprem server stack with no smart tech over all of my disks (no RAID or ZFS). I was wondering if anything is currently in the works for handling node deployments to with host paths (say to individual disks) or if this is already supported, getting a nudge in the right direction. I am planning on eventually adding a HDD and SSD tier with host paths and trying to evaluate if foregoing the operator and managing the k8s configs manually is the way to go at the present time.

Thanks!

[chrislusf]

volumeServerDiskCount is like a physical disk count.

seaweedfs-operator/controllers/controller_volume_statefulset.go

Line 45 in 1053ae7

for i := 0; i < volumeCount; i++ {

there are no assumption for special type of RAID or file system.

[ProjectInitiative]

Gotcha, so if one wanted to specify multiple "disks" with this operator, would multiple volume specs provide this functionality?