Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi region / Multi Data Center Support #5467

Closed
senthilsivanath opened this issue Dec 18, 2020 · 8 comments
Closed

Multi region / Multi Data Center Support #5467

senthilsivanath opened this issue Dec 18, 2020 · 8 comments

Comments

@senthilsivanath
Copy link

senthilsivanath commented Dec 18, 2020

/kind question

Question:
Does kubeflow play well for multi cluster setup, i.e when there are multiple installations of kubeflow in multiple data center / regions connecting to same MYSQL (cross region) and GCS multi region

Example :

Kubeflow Cluster 1 - US East
kubeflow Cluster 2 - US West

MySQL State store (Active (US East) -> Passive (US West))
GCS (multi region)

Additional Loadbalancer across region level distributes the traffic, obviously all the setting needs be applied at both cluster level.

Questions

  1. Is this setup recommended
  2. Does it produce any inconsistency when one / more component works i.e kubeflow pipelines where steps are executed and kfp clients distribute traffic between two clusters.

Any kubeflow cluster setting change has to be applied at both cluster level independently, any other caveats in multi cluster setup. Couldn't find related details in kubeflow documentation.

Can both cluster be Active / Active or should it be Active / Passive ?

@jbottum
Copy link
Contributor

jbottum commented Dec 18, 2020

@senthilsivanath Thanks for your question. East/West Active/Active replication of your entire Kubeflow data science environment will often result in cost and performance concerns. We might try to whiteboard your use cases and architect a data management solution to meet your RTO/RPO, performance & budget requirements. Arrikto is a leading code contributor to Kubeflow and its data management solution provides a full featured, standards-based, scale-out architecture, which is described here, https://www.arrikto.com/rok-data-management/. I would be glad to set-up some time to discuss with our SMEs.

@jbottum
Copy link
Contributor

jbottum commented Jan 8, 2021

/priority p2
/area installation
/platform gcp

@jbottum
Copy link
Contributor

jbottum commented Jan 8, 2021

@senthilsivanath Hi, did you find an architecture / configuration to support your requirements ?

@kubeflow-bot kubeflow-bot removed this from To Do in Needs Triage Jan 8, 2021
@senthilsivanath
Copy link
Author

@jbottum not really.

@jbottum
Copy link
Contributor

jbottum commented Jan 8, 2021

@senthilsivanath would you like to set-up a time to discuss with some Kubeflow / Data Management SMEs, perhaps next Friday, Jan 15?

@jbottum
Copy link
Contributor

jbottum commented Jan 12, 2021

@senthilsivanath checking back to see if you would like to discuss this architecture. you might check out Rok (and the Rok Registry) which are based on a K8s storage class and enable your data science environment (ML code, data, metadata, and dependencies) to be re-created in another cluster, https://www.arrikto.com/rok-data-management/

@stale
Copy link

stale bot commented Jun 3, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the lifecycle/stale label Jun 3, 2021
@stale stale bot closed this as completed Jun 11, 2021
@RakeshRaj97
Copy link

Any updates on this use case?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants