Problem
As of now, Kubernetes backend works against a single cluster specified in current-context in kubeconfig. Since there can be one Kubernetes backend per project, dstack users cannot work with multiple Kubernetes clusters inside one project. Having multi-cluster support brings many benefits:
- More compute capacity.
- Quick switching between clusters and namespaces.
- Multi-region support for Kubernetes.
- A differentiator to plain Kubernetes that does not allow submitting workloads to many clusters simultaneously (kubectl always works against a specific cluster).
Solution
https://docs.google.com/document/d/1xuOCYQgSwPODqFZ-y3Ir7gTfgZWjsBTK5ej95H20Rnw
Workaround
No response
Would you like to help us implement this feature by sending a PR?
Yes
Problem
As of now, Kubernetes backend works against a single cluster specified in current-context in kubeconfig. Since there can be one Kubernetes backend per project, dstack users cannot work with multiple Kubernetes clusters inside one project. Having multi-cluster support brings many benefits:
Solution
https://docs.google.com/document/d/1xuOCYQgSwPODqFZ-y3Ir7gTfgZWjsBTK5ej95H20Rnw
Workaround
No response
Would you like to help us implement this feature by sending a PR?
Yes