Closed ealyn closed 1 year ago
Check if you reproduce this using the main branch, we have quite a few changes since last release i think.
KubeIngressProxy isn't something we have capacity to maintain well :/
Check if you reproduce this using the main branch, we have quite a few changes since last release i think.
KubeIngressProxy isn't something we have capacity to maintain well :/
Related code that add_route calling _expand_user_properties are same between 4.3.0 and main. I know KubeIngressProxy is not the focus, but I prefer ingress-nginx than CHP. After solved some little problems, KubeIngressProxy 1.1.0 (in z2jh 1.5.0) works very well in a couple of month. Now I'm trying upgrade to newest z2jh 2.0.0.
Closed by #731, will be released in 6.0.0 to be released soonish
Bug description
I can not startup z2jh with KubeIngressProxy(4.3.0), the hub pod is CrashLoopBackOff, and got these log:
Expected behaviour
Actual behaviour
It seems that hub route data is
{"hub": true}
, but functionKubeIngressProxy:_expand_user_properties
try to getuser
from it.How to reproduce
Just set
c.JupyterHub.proxy_class = "kubespawner.proxy.KubeIngressProxy"
and then helm install jupyterhub.Your personal set up
Full environment
``` # paste output of `pip freeze` or `conda list` here ```Configuration
```python # jupyterhub_config.py ```Logs
``` # paste relevant logs here, if any ```