# Multi-zone jupyterhub in GKE

**URL:** https://discourse.jupyter.org/t/multi-zone-jupyterhub-in-gke/786
**Category:** Zero to JupyterHub on Kubernetes
**Created:** [April 11, 2019, 3:50pm UTC](https://discourse.jupyter.org/t/multi-zone-jupyterhub-in-gke/786 "2019-04-11T15:50:18Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![brevans](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/brevans/32/442_2.png) [@brevans](https://discourse.jupyter.org/u/brevans)
#### Post date: [April 11, 2019, 3:50pm UTC](https://discourse.jupyter.org/t/multi-zone-jupyterhub-in-gke/786/1 "2019-04-11T15:50:18Z")

</div>

Background:

Past few weeks we have been running into scaling issues for a couple 5-15 node single-zone autoscaling GKE clusters running jupyterhub v0.8.0. In both cases we see autoscaling getting triggered when expected but occasionally failing with `ZONE_RESOURCE_POOL_EXHAUSTED`, which I gather means the zone we are running in is out of compute for us. Of course these are times mid-day when the cluster is acutely needed. It’s relatively straight-forward to get new nodes in a different zone, but the persistent storage volumes are locked to the current zone as far as I can tell.

Questions:

- anyone else run into this?
- is there a way to have user volumes float across a region though configuration to gcloud / jupyterhub’s helm config?
- is there a sane way to take what we have and make it multi-zonal without tearing everything down?

---

<div class="post-metadata">

### Author: ![espine](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/espine/32/1383_2.png) [@espine](https://discourse.jupyter.org/u/espine)
#### Post date: [April 11, 2019, 8:53pm UTC](https://discourse.jupyter.org/t/multi-zone-jupyterhub-in-gke/786/2 "2019-04-11T20:53:22Z")

</div>

I could be wrong but I think this message is in regards to a resource quota you may have exceeded. I have run into these in the past and have requested to increase the quota without a hassle.

---

<div class="post-metadata">

### Author: ![brevans](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/brevans/32/442_2.png) [@brevans](https://discourse.jupyter.org/u/brevans)
#### Post date: [April 12, 2019, 4:28pm UTC](https://discourse.jupyter.org/t/multi-zone-jupyterhub-in-gke/786/3 "2019-04-12T16:28:35Z")

</div>

Pretty sure this isn’t the case, as the cluster sizes have been larger both before and after these events. My understanding is that the quotas are static unless you explicitly ask for them to be changed.
