[QUESTION] Capacity quota always set even when undefined using Nomad

[FredPraca]

I'm currently using juicefs over a Minio cluster in the context of Nomad orchestration.

When declaring the volume like this :

type      = "csi"
id        = "prometheus-volume"
name      = "prometheus-volume"
namespace = "demo-services"

capability {
  access_mode     = "multi-node-multi-writer"
  attachment_mode = "file-system"
}
plugin_id    = "juicefs0"

secrets {
  name       = "juicefs-volume"
  metaurl    = "postgres://juicefs_user:[email protected]:5432/juicefs?sslmode=disable"
  bucket     = "http://127.0.0.1:9000/nomad/"
  storage    = "minio"
  access-key = "my-access-key"
  secret-key = "my-secret-key"
}

IP addresses were changed.

I get this in the quota definitions:

+------------------------------+---------+---------+------+-----------+-------+-------+
|             Path             |   Size  |   Used  | Use% |   Inodes  | IUsed | IUse% |
+------------------------------+---------+---------+------+-----------+-------+-------+
| /prometheus-volume           | 1.0 GiB | 297 MiB |  28% | unlimited |    94 |       |
+------------------------------+---------+---------+------+-----------+-------+-------+

I thought that no quota would be applied as capacity_min and capacity_max are optional parameters.

Environment:

• JuiceFS CSI Driver version : v0.23.6
• Nomad version : 1.8.1
• Object storage (cloud provider and region): Minio on prem
• Metadata engine info: Postgresql
• Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage): Postgresql on the same machine as one of the Minio machine