-
Notifications
You must be signed in to change notification settings - Fork 63
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
Make regional deployments work; what to do about the disks for metadata #6
Comments
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
/kind feature |
Is there an update on work for this as this is a highly desirable feature for enterprise installations |
Hi @damitkwr, thanks for your interest. Thumbs up on the issue give us more metrics to prioritize them. |
Interested in regional as well! |
We've supported regional clusters in Kubeflow 1.3 on Google Cloud by switching to use CloudSQL + GCS by default. |
We would like to support regional deployments of Kubeflow; i.e. use a regional cluster. Ideally this would be the default deployment since regional clusters are more reliable and there is minimal cost savings to using a zonal cluster.
One issue we need to resolve is what to do about the disks backing up the metadata DB.
We should be able to use regional PDs.
https://cloud.google.com/compute/docs/disks/high-availability-regional-persistent-disk
EDIT: please thumbs up on the issue if it's important to you.
The text was updated successfully, but these errors were encountered: