Binderhub deploy 404 when connecting to jupyterhub

[ctr26]

At the step where one connects jupyterhub to binderhub I get a 404.

kubectl --namespace=<namespace-from-above> get svc proxy-public

This step doesn't work on my cluster as our ingress controller is slightly different (same for minikube). What I can do is port forward the public proxy to 127.0.0.1:8000 which when I visit it gives me the same screen as visiting https://hub.mybinder.org/, all expected behaviour. When I try to update the binderhub config to use this port address:

config:
  BinderHub:
    hub_url: http://127.0.0.1:8000/
    # hub_url: https://hub.mybinder.org/
    base_url: /binderhub
    use_registry: true
    image_prefix: bioimagearchive/binder-

ingress:
  enabled: true
  hosts:
    - ""
    - localhost

I get a 404 error, same happens if I drop in a link to the hub at mybinder. Exactly the same happens if I use the internal IP address. I assumed it was a secrets problem but I've generated keys for this several times now:

jupyterhub:
  hub:
    services:
      binder:
        apiToken: "<output of FIRST `openssl rand -hex 32` command>"
  proxy:
    secretToken: "<output of SECOND `openssl rand -hex 32` command>"

Any advice very welcome at this point and apologies if this belongs in the binderhub repo.

Best

Craig

[welcome]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.

You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

[manics]

Hi @ctr26!

BinderHub runs in a separate container from JupyterHub, so

hub_url: http://127.0.0.1:8000/

won't work, you'll need to use an IP or DNS that works both inside and outside the k8s cluster.

As it happens I also ran into a related(?) problem for other reasons and ended up patching BinderHub so it could use the internal service DNS for binderhub-jupyterhub communication, and the external address for users:
jupyterhub/binderhub#994
Feel free to add your thoughts there if it's useful.

In general we ask that JupyterHub GitHub issues are used for bugs and development discussions, with support being handled on the community forum where more people hang out, and the rest of the community can benefit from these discussions. Hope you understand 😀.

[support]

Hi there @ctr26 👋!

I closed this issue because it was labelled as a support question.

Please help us organize discussion by posting this on the http://discourse.jupyter.org/ forum.

Our goal is to sustain a positive experience for both users and developers. We use GitHub issues for specific discussions related to changing a repository's content, and let the forum be where we can more generally help and inspire each other.

Thanks you for being an active member of our community! ❤️