Repository navigation
seaweedfs: tenant maxVolumes is hardcoded in four places and unasserted #4245
Description
packages/extra/seaweedfs/templates/seaweedfs.yaml hardcodes maxVolumes: 0 in four places: lines 251, 270, 286 and 311, covering the default volume server, pools, zones and zone-pools.
That zero is what makes a volume server derive its slot count from free disk. Drop it and the vendored chart falls back to 7, so the server reports seven slots no matter how large the PVC is.
extra/seaweedfs overrides dataDirs for every real instance, so those four lines are what a tenant actually renders, not the defaults in packages/system/seaweedfs/values.yaml. Nothing under packages/extra/seaweedfs/tests/ asserts any of them.
A change to any of the four therefore caps the instance at seven volume slots per server and nothing catches it. The rendered -max is the thing worth asserting, not the values key.
Activity
fix(seaweedfs): raise the bucket ceiling by sizing volumes smaller (c…