If the url is the wrong thing, I would love a suggestion. Regardless, the helm installation succeeds, and I see
kubectl get all -n hubtraf
NAME READY STATUS RESTARTS AGE
pod/collector-7c44468b74-gbb77 1/1 Running 0 10m
pod/hubtraf-hubtraf-htqml 1/2 Running 0 10m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/collector ClusterIP 10.100.210.235 <none> 24224/TCP 10m
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/collector 1/1 1 1 10m
NAME DESIRED CURRENT READY AGE
replicaset.apps/collector-7c44468b74 1 1 1 10m
NAME COMPLETIONS DURATION AGE
job.batch/hubtraf-hubtraf 0/1 10m 10m
However, all of the logs suggest that it is using "LTI" login by default: <ClientResponse(https://icesat-2.hackweek.io/hub/lti/launch) [404 Not Found]>, but I can't figure out why it chooses this over dummy auth.
I have been trying to get a hubtraf to test a JupyterHub.
I
git clone
the repo,cd hubtraf
, and runIf the url is the wrong thing, I would love a suggestion. Regardless, the
helm
installation succeeds, and I seeHowever, all of the logs suggest that it is using "LTI" login by default:
<ClientResponse(https://icesat-2.hackweek.io/hub/lti/launch) [404 Not Found]>
, but I can't figure out why it chooses this over dummy auth.Thoughts?