JupyterHub custom domain does not persist and is not reachable
Summary
When one updates domain to use a custom domain, after a few sec the domain changes back to <ip>.nip.io
domain
In the event one clicks "install" prior to the change ocurring, the app is not reachable on the designated URL.
Steps to reproduce
- Change default URL
- Click save prior to automatically changing back to default
- Try to reach app on designated URL
What is the current bug behavior?
- Custom URL does not remain
- Custom URL is not reachable
What is the expected correct behavior?
- Custom URL remains
- Custom URL is reachable
Relevant logs and/or screenshots
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
)
Possible fixes
From https://gitlab.com/gitlab-org/gitlab-ce/issues/59740#note_158124856
There's 2 issues,
The UI needs to stop reloading default ingress endpoint so as to let user type in the overwrite.
Once installed with overwritten domain, I couldn't access JH on the ingress ip (jupyter.[ip].nip.io) so I'm not sure what CNAME to forward to. Meanwhile JH was available on proxy-public (the extra load balancer)
Edited by Daniel Gruesso