Open Gregory-Pereira opened 1 year ago
So interestingly, the first network request actually gets all the sizing data in a comfigmap and then makes a request to each individual sizing configuration, however despite returning with a 403 you the URL it used does indeed reach the configurations listed.
Seems that the deployment is bassed off the replica controller which stores the full encoded deployment config in metadata in the openshift.io/encoded-deployment-config
annotation. This looks for the Jupyterhub-cfg
configmap. From the deployment config:
- name: SINGLEUSER_PVC_SIZE
valueFrom:
configMapKeyRef:
name: jupyterhub-cfg
key: singleuser_pvc_size
This is the request it makes to get the value: https://jupyterhub-odh-jupyterhub.apps.odh-cl2.apps.os-climate.org/services/jsp-api/api/user/configmap
Stalls notebook provisioning to an unreasonable degree. Google networking console reveales 403 cannot get resource sizing reqs for a new notebook. Affects all notebook types but demoed with elyra.
Follow on issue: opening a bunch of jupyterhub notebooks simultaneous throws 502. Will look into this after inital steps are taken to search for this issue in the upstream (assign @MichaelTiemann).
/assign