🤔 Problem

Having access to batch job is a request we have received from many users but particularly from the academic team. Batch jobs are workloads that do not have a UI. This is a job that runs on Renku without a frontend.

🍴 Appetite

6 weeks

🎯 Solution

[Flora] Very important consideration: this is all about re-using Amalthea and the existing Amalthea session CRD to support running offline jobs. This has the advantage of bringing in all the existing Renku “goodies”: git repositories, data connectors, admin monitoring, etc.

🚞 User stories / journeys

• Enable launching, listing, deleting, getting logs for jobs with the CLI
• We can save on effort by adding this only as a capability to the CLI
• The API can be simple - pick a resource class and launch any image with those requirements. This allows us to control usage and access to compute.
• Limitations on user IDs and groups IDs in the image - you still run as non root.
• The CLI can query the data service API for logs.
• The web UI fully ignores jobs (for now)
• Nice to have: Newer versions of K8s use websockets for kubectl exec - can we then have a proxy for this that autheticates requests from the CLI and routes them to the right job?

🐰 Rabbit Holes

🔐 Security Implications