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
Instead of relying on Argo-Workflows as a backend, could we rely on the Kubernetes Job and CronJob objects instead? They perform very similar functions.
The reason why we didn't do this initially was because we are relying on the Nebari-Workflow-Controller to modify the Argo-Workflow (to mount the user's home directory, etc.). So in order to use the Kubernetes Jobs/CronJobs, we will need to generalize the NWC to allow it modify those additional resources.
The text was updated successfully, but these errors were encountered:
Instead of relying on Argo-Workflows as a backend, could we rely on the Kubernetes Job and CronJob objects instead? They perform very similar functions.
The reason why we didn't do this initially was because we are relying on the Nebari-Workflow-Controller to modify the Argo-Workflow (to mount the user's home directory, etc.). So in order to use the Kubernetes Jobs/CronJobs, we will need to generalize the NWC to allow it modify those additional resources.
The text was updated successfully, but these errors were encountered: