Current behaviour

The CPU and Disk quota for users can be set through command-line by REANA administrators:

kubectl exec -i -t deployment/reana-server -c rest-api -- flask reana-admin quota-set -e [email protected] -r disk -l 429496729600 --admin-access-token $REANA_ADMIN_ACCESS_TOKEN

This is perfectly fine, however for certain deployment scenarios, one would like to achieve this over REST API without having direct Kubernetes cluster access, so that first support line could manage user quotas without having any cluster privileges.

Desired behaviour

It would be therefore good to introduce new REST API endpoints that would allow to consult and set the quota for users remotely.

This new REST API should be accessible only after providing certain secret which is not necessarily the same as REANA_ADMIN_ACCESS_TOKEN. This will allow to support scenarios where the frontend support line could be granted rights to manage user quotas without having access to much else.

This secret could be set in a Helm value. And, if the secret would be empty (default value), this functionality would be disabled (and so quota management would be only available from the command line, as is the case now).

The calling of the new REST API endpoints could be simply via curl commands. (We don't need to enrich reana-client.) The admin documentation under docs.reana.io should then be updated accordingly.