Closed Boes-man closed 5 years ago
This appears to be due to a lack of git
on the kubernetes host. As we use the gitRepo
volume type it is required for Pangeo.
I'm wondering if this is due to the age of your Kubernetes cluster. The gitRepo
volume type has been deprecated in favour of an init container performing the same function to remove the git
dependency from Kubernetes. Therefore we should make this change in Pangeo.
However for now as a workaround you could ensure git
is installed on the host.
Ok I am on 1.12.3 I am off for a week but will test and let you know.
Thanks
Hey @jacobtomlinson git was already installed on all the hosts, so I updated jupyter_config.yaml and converted the volumes to emptydir and initcontainer spec. The helm deploy completes now, but I am not getting a public ip. This might be because my ingress controller is traefik?
kubectl --namespace=pangeo get svc proxy-public NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE proxy-public LoadBalancer 10.100.211.118 pending 80:32638/TCP 43s
kubectl --namespace=pangeo get pod NAME READY STATUS RESTARTS AGE hub-7b8bbb65f8-m6zv7 1/1 Running 0 8m25s proxy-7746576cb7-mcpr5 1/1 Running 0 8m25s
Again this is likely to be due to your cluster configuration and not Pangeo.
If you're using an ingress controller I would expect the controller to get an IP, not the hub service. Then it would use DNS entries to forward traffic internally.
OK, looks like its "up". Is there any basic/quickstart type guide so I can verify its ok?
what i get after clicking Start My Server
There are example notebooks you can run once your server is started. However it looks like you're not getting that far. Check the logs from the notebook pod to see what the issue is.
logs-from-notebook-in-jupyter-pub-2dgit-2dtester.txt Had to bump resource for the kube cluster nodes. Start My Server does launch the notebook pod but getting a different 500 error (redirect loop)...? Home page now shows Stop my server and My server. Hitting My server results in 500 error (redirect loop).
Also wondering whether these settings matter in the jupyter_config.yaml ` storage: extraVolumes:
Seeing javascript error in my browser console? Javascript is allowed in the browser and I have also added the site ip as specifically allowed. Both chrome and firefox have same error.
OK, result! My ingress needed to be for proxy-public service not the hub service.
Thanks for the assistance and patience :)
No problem! I'm glad you've managed to get it working. Please let us know what you're doing with it!
Hello, got my dynamic PV storageclass for my kube cluster lab working. Now seeing an different mount error, as per the attached.
Thanks