Spawn failed: Timeout even when start_timeout is set to 3600 seconds

JupyterHub Zero to JupyterHub on Kubernetes
18

I’ve reduced my config.yaml down to the bare minimum to see if that helps:

debug:
  enabled: true

hub:
  config:
    JupyterHub:
      authenticator_class: dummy
      log_level: DEBUG
    Authenticator:
      admin_users:
        - daniel
      allowed_users:
        - student1
    DummyAuthenticator:
      password: (redacted)

singleuser: 
  
  # `cmd: null` allows the custom CMD of the Jupyter docker-stacks to be used
  # which performs further customization on startup.
  cmd: null

  # Setting a global start_timeout instead of 'per profile'
  startTimeout: 3600
  
  # Default to base image
  #image:
  #  name: jupyter/scipy-notebook
  #  tag: latest

  #storage:
  #  dynamic:
  #    storageClass: "standard"
  #  capacity: 2Gi

  #cpu:
  #  limit: 1
  #  guarantee: .5 

  #memory:
  #  limit: 2G
  #  guarantee: 2G

What’s interesting is I can’t seem to get debug logs that show what the error might be in the spawning process.

These are my listed nodes:

continuous-image-puller-4pxch     1/1     Running   0          23m
continuous-image-puller-5d8tt     1/1     Running   0          23m
continuous-image-puller-ssb6q     1/1     Running   0          23m
hub-5f5fc74974-k9w8b              1/1     Running   0          3m17s
jupyter-student1                  0/1     Pending   0          2m20s
proxy-5b4b6fcc-9p5lr              1/1     Running   0          3m17s
user-scheduler-7bf8fbbcd8-9kx2j   1/1     Running   0          23m
user-scheduler-7bf8fbbcd8-sphx6   1/1     Running   0          23m

But when I use kubectrl logs -f on each, none of them provide any debug logging from JupyterHub that would elucidate what’s going on. Hmm…