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
More and more organizations are managing Kubernetes in a multi-cluster setup to effectively manage capacity and workload placement. For instance, we can find a few initiatives:
Currently, Kubeflow Training doesn't offer any best practices for managing TrainJobs across multiple Kubernetes clusters.
Our Python SDK fully relies on kubeconfig or Access Token to communicate with Kubernetes API server.
I would like to initiate this discussion to explore various options for enabling ML Engineers and Data Scientists to interact with Kubeflow TrainJobs in a multi-cluster environment.
What you would like to be added?
More and more organizations are managing Kubernetes in a multi-cluster setup to effectively manage capacity and workload placement. For instance, we can find a few initiatives:
Currently, Kubeflow Training doesn't offer any best practices for managing TrainJobs across multiple Kubernetes clusters.
Our Python SDK fully relies on
kubeconfig
or Access Token to communicate with Kubernetes API server.I would like to initiate this discussion to explore various options for enabling ML Engineers and Data Scientists to interact with Kubeflow TrainJobs in a multi-cluster environment.
cc @kubeflow/wg-training-leads @saileshd1402 @Electronic-Waste @seanlaii @kannon92 @astefanutti @bigsur0 @akshaychitneni @shravan-achar
Love this feature?
Give it a 👍 We prioritize the features with most 👍
The text was updated successfully, but these errors were encountered: