Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Check out Argo Workflows.
I recommend you just stick with HPC centric tools are workflows. Your scientists aren’t going to learn k8s as you said. SLURM is the scheduler you want and if you’re new to HPC, I recommend taking a look at https://openhpc.community
Lawrence Livermore National lab is working on a project called Flux that has a kubernetes operator - https://github.com/flux-framework/flux-operator
Do you have a reason to use kubernetes besides it’s the $CURRENT tech? Why not stick with what you’re already familiar with (batch job managers) and use SLURM, a workload and resource manager, like many others in HPC? Do the researchers need to schedule against Nvidia GPU resources now or in the future? Nvidia themselves recommend SLURM.
Armada could be an alternative: https://armadaproject.io/