helm: add quota limit 0 = unlimited to README

Closes reanahub/reana-server#625

AUTHORS.rst

@@ -7,6 +7,7 @@ The list of contributors in alphabetical order:
 - `Anton Khodak <https://orcid.org/0000-0003-3263-4553>`_
 - `Audrius Mecionis <https://orcid.org/0000-0002-3759-1663>`_
 - `Camila Diaz <https://orcid.org/0000-0001-5543-797X>`_
+- `Daan Rosendal <https://github.com/DaanRosendal>`_
 - `Dan Leehr <https://orcid.org/0000-0003-3221-9579>`_
 - `Daniel Prelipcean <https://orcid.org/0000-0002-4855-194X>`_
 - `Diego Rodriguez <https://orcid.org/0000-0003-0649-2002>`_

helm/reana/README.md

@@ -122,8 +122,8 @@ This Helm automatically prefixes all names using the release name to avoid colli
 | `quota.enabled` | Enable user workflow accounting capabilities. | true |
 | `quota.periodic_update_policy` | Cronjob pattern representing how often the users Disk and CPU quota usage should be updated. Leave it empty to deactivate it | "0 3 * * *" |
 | `quota.workflow_termination_update_policy` | Resources to calculate quotas on worflow termination. Possible values: "cpu" and "disk". Leave it empty to deactivate workflow termination accounting. | "" |
-| `quota.default_disk_limit` | Default users disk quota limit in bytes.    | None |
-| `quota.default_cpu_limit` | Default users CPU quota limit in milliseconds.    | None |
+| `quota.default_disk_limit` | Default users disk quota limit in bytes. (0=unlimited) | 0 |
+| `quota.default_cpu_limit` | Default users CPU quota limit in milliseconds. (0=unlimited) | 0 |
 | `workspaces.retention_rules.maximum_period` | Set a default period in days for workspace retention rules. Users will not be able to specify a longer period to retain the workspace files. After this period the workspace will be cleared. To disable the period and allow files to be kept forever, use value "forever". | forever |
 | `workspaces.retention_rules.cronjob_schedule` | Cron format string describing how often pending retention rules should be applied. | "0 2 * * *" |
 | `workspaces.paths` | List of additional workspace paths as strings. Each mount string is composed by a key `hostPath`(path to the directory to be mounted from the Kubernetes nodes) and a cluster_pod_mountpath (path inside the cluster containers where the `mountPath` will be mounted) e.g. `hostPath:mountPath`. The first value listed will be the default workspace root path. Any POSIX filesystem mounted on cluster nodes is supported | None |