Looking for advice on migrating from Classic to Operator: cross K8s cluster schedulers #9962
Unanswered
champialex
asked this question in
Q&A
Replies: 1 comment
-
Apologies, just realised that there was a big red banner about posting on discourse. Have posted there |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey all,
So, we have implemented a layer on top of the classic KubeCluster to allow running an heterogenous adaptive scheduler, with several different KubeClusters.
One of the cool thing it supports is scheduling jobs in AWS and on prem (or on another K8s cluster) within the same dask scheduler (let's say easy and flexible access to fancy GPUs or to large RAM, or ...)
It seems that the new operator API will be a nice way to support multiple groups, and maybe with a bit of customisation, adaptive scaling as well, but I'm not sure of what the best way would be to handle cross-cluster scheduling.
Any advice?
Beta Was this translation helpful? Give feedback.
All reactions