You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like creator label will be applied to workflows created by cron workflows. Also, creator label should be on resubmitted workflows. This should simplify things.
Hi @terrytangyuan, Nebari Workflow Controller is only used by Nebari. There is a video demo of Nebari on https://quansight.com/nebari-services/. Nebari is an open source data science platform and implemented on top of JupyterHub, Argo Workflows, and other open source tools. With Nebari Workflow Controller, I'm trying to restrict what users can do with their Argo Workflows (which VolumeMounts they have access to, but perhaps other restrictions down the line) as well as provide some convenience features to make the Argo experience similar to the experience that users have when using Nebari's default jupyterlab experience (e.g. mount the same python environments and NFS drives, set the same environment variables). The closest thing to a demo of Nebari Workflow Controller would probably be this example in the docs.
Looks like creator label will be applied to workflows created by cron workflows. Also, creator label should be on resubmitted workflows. This should simplify things.
argoproj/argo-workflows#11381
The text was updated successfully, but these errors were encountered: