PodUnschedulable Cannot schedule pods: pod has unbound immediate PersistentVolumeClaims.

[FasihZafar]

Hi all, I'm running into the following error while launching a repo. Any ideas on how to resolve this. Thanks
Repo: https://github.com/binder-examples/r
My config.yaml:

binderhub:
  config:
    BinderHub:
      hub_url: http://<hubip>
      use_registry: true
      image_prefix: <dockerusername/binderhub->

  jupyterhub:
    hub:
      services:
        binder:
          # where binder runs
          url: "http://<binderip>"        
          apiToken: <token>
          oauth_redirect_uri: "http://<hubip>/services/binder/oauth_callback"
          oauth_client_id: "binder-oauth-client-test"

      config:
        JupyterHub:
          authenticator_class: dummy      

    proxy:
      secretToken: <token>

    singleuser:
      storage:
        dynamic:
          storageClass: <name for my storage class>

  registry:
    username: <dockerusername>
    password: <password>

[FasihZafar]

This is the reason for the error that gke is showing. The Pod’s Persistent Volume Claims are not bound to a volume. This error might happen if your Persistent Volume is not provisioned. I'm trying to deploy on gke

[arnim]

Unfortunately, I've never done an install on GKE. @ctr26 mentioned as one of the cons that it can be at times a bit fiddly to install.

Not sure if it helps in the short run... but @damianavila and I will probably meet next week to discuss ways to make dynamic image building more easily accessible

[arnim]

@FasihZafar have you tried JHub on GKE? If I remember correctly this might be similar to a z2jh config.yaml and there seem to be discussions around a related issue.

[FasihZafar]

Thanks @arnim I was able to resolve this by recreating a storage class