Question: how to change machine type of an existing JupyterHub on K8s

[mr_z_ro]

It appears this was a similar case (but perhaps not identical) where indeed the solution was to set up a custom storage class config:

Problem with Spawning Pods with Persistent Volumes in a Multi-Zonal GKE deployment

We are running Z2JK (Zero to Jupyterhub on Kubernetes) on a multi-zonal GKE cluster. We noticed that during the Spawning process the Pod’s persistent volume is being provisioned in an availability zone that is different than the availability zone where the Pod is being provisioned (Spawned). This causes the POD to crash and Jupyterhub to log a “spawner timeout error”. Is there any way to tell Z2JK to provision the pod’s persistent volume in the same availability zone where the Pod is being …

And indeed the docs have some notes on GKE and defaults as well, with instructions on how to set that up:

Customizing User Storage