Skip to content
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

Explore Kubernetes Job and CronJob #1

Open
iameskild opened this issue Aug 30, 2023 · 1 comment
Open

Explore Kubernetes Job and CronJob #1

iameskild opened this issue Aug 30, 2023 · 1 comment

Comments

@iameskild
Copy link
Member

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.

@Adam-D-Lewis
Copy link
Member

Adam-D-Lewis commented Mar 5, 2024

I'd like to look into this. Another advantage of using k8s Jobs/CronJob is we could split out Argo Workflows from Nebari and make it an extension.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants