-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
helm: administrators to choose allowed workspace options #532
Closed
Comments
marcdiazsan
added a commit
to marcdiazsan/reana
that referenced
this issue
Aug 24, 2021
marcdiazsan
added a commit
to marcdiazsan/reana-commons
that referenced
this issue
Aug 24, 2021
marcdiazsan
added a commit
to marcdiazsan/reana-db
that referenced
this issue
Aug 24, 2021
…en the workspace root path is not declared Closes reanahub/reana#532
This was referenced Aug 24, 2021
marcdiazsan
added a commit
to marcdiazsan/reana
that referenced
this issue
Aug 26, 2021
marcdiazsan
added a commit
to marcdiazsan/reana-server
that referenced
this issue
Aug 26, 2021
Goes on top of reanahub/reana-client#545 PR set, and reanahub/reana#532 PR set Closes reanahub/reana-client#546
marcdiazsan
added a commit
to marcdiazsan/reana-commons
that referenced
this issue
Aug 26, 2021
Goes on top of reanahub/reana-client#545 PR set, and reanahub/reana#532 PR set Closes reanahub/reana-client#546
This was referenced Aug 26, 2021
marcdiazsan
added a commit
to marcdiazsan/reana
that referenced
this issue
Sep 4, 2021
marcdiazsan
added a commit
to marcdiazsan/reana
that referenced
this issue
Sep 4, 2021
marcdiazsan
added a commit
to marcdiazsan/reana
that referenced
this issue
Sep 4, 2021
marcdiazsan
added a commit
to marcdiazsan/reana-commons
that referenced
this issue
Sep 5, 2021
marcdiazsan
added a commit
to marcdiazsan/reana-commons
that referenced
this issue
Sep 5, 2021
Goes on top of reanahub/reana-client#545 PR set, and reanahub/reana#532 PR set Closes reanahub/reana-client#546
marcdiazsan
added a commit
to marcdiazsan/reana-server
that referenced
this issue
Sep 5, 2021
Goes on top of reanahub/reana-client#545 PR set, and reanahub/reana#532 PR set Closes reanahub/reana-client#546
marcdiazsan
added a commit
to marcdiazsan/reana
that referenced
this issue
Sep 6, 2021
marcdiazsan
added a commit
to marcdiazsan/reana
that referenced
this issue
Sep 7, 2021
…ce exposure for admins Closes reanahub#532
marcdiazsan
added a commit
to marcdiazsan/reana
that referenced
this issue
Sep 10, 2021
marcdiazsan
added a commit
to marcdiazsan/reana
that referenced
this issue
Sep 11, 2021
marcdiazsan
added a commit
to marcdiazsan/reana
that referenced
this issue
Sep 11, 2021
marcdiazsan
added a commit
to marcdiazsan/reana
that referenced
this issue
Sep 13, 2021
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When deploying REANA, users can run workflows on several workspaces. Right now, any POSIX filesystem mounted on cluster nodes is supported.
In theory, users could ask for any such mounted filesystem:
In practice, the administrators should limit what is allowed to use.
For example, empty value is allowed and it will use the default shared filesystem (
/var/reana/users/aaaa/workflows
), or/myshareddisk/
is allowed, etc.This issue is about allowing REANA cluster administrators to easily choose the available prefix values via Helm. We need a new variable for
helm/reana/README.md
named for exampleworkspaces.paths
that would be a list of available path prefixes, the first being the default.The cluster would then mount automatically these values to all the necessary pods.
P.S. The users would choose which one to use via
reana.yaml
, see another issue reanahub/reana-client#545The text was updated successfully, but these errors were encountered: