configuring ingress for dask-jupyter helm chart deployment #8417
Unanswered
b-weintraub
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I deployed a single-user dask-jupyter helm chart on a k8s cluster (https://github.com/dask/helm-chart/tree/main/dask).
$ helm ls
$ kubectl get svc pangeo-dask-jupyter pangeo-dask-scheduler
I'm trying to expose an external ip. My k8s does not allow the use of the LoadBalancer service so I'm trying to enable the ingress instead.
For exposing an external ip, I’m trying to enable ingress following this template:
https://github.com/dask/helm-chart/blob/main/dask/templates/dask-jupyter-ingress.yaml
Here’s the ingress part of my values.yaml:
When I run the update, here’s my error:
$ helm upgrade pangeo -f values.yaml dask/dask
Error: UPGRADE FAILED: YAML parse error on dask/templates/dask-jupyter-ingress.yaml: error converting YAML to JSON: yaml: line 19: mapping values are not allowed in this context
Does anyone have any suggestions for configuring the YAML for ingress?
Beta Was this translation helpful? Give feedback.
All reactions