search

nebari-dev / nebari-workflow-controller

A WIP kubernetes admission controller to control what workflows can be deployed by which users
BSD 3-Clause "New" or "Revised" License
0 stars 2 forks source link

Make modifications to accomodate latest Argo Workflows release #21

Open Adam-D-Lewis opened 11 months ago

Adam-D-Lewis commented 11 months ago

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.

https://github.com/argoproj/argo-workflows/issues/11381

terrytangyuan commented 11 months ago

Interesting project! Is there a demo yet?

Adam-D-Lewis commented 11 months ago

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.

terrytangyuan commented 11 months ago

Sounds great!