-
Notifications
You must be signed in to change notification settings - Fork 786
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https entry point? #43
Comments
Tracked in jupyterhub/helm-chart#14 |
This has been fixed by #229! |
@yuvipanda does #229 explicitly require purchasing a domain name from a registrar? (as explained https://zero-to-jupyterhub.readthedocs.io/en/v0.5-doc/security.html#https) What I'd like to do is access the Example: |
@masonlr yeah, it does require an external domain name purchased. This is because we use https://letsencrypt.org/ to provision HTTPS certificates, and they require a domain name. This is the case for most HTTPS certificate providers - they won't provide you HTTPS certificates for IPs. CLUSTER-IP is also usually only accessible from inside the cluster, and (unless your cluster is configured in specific ways that most clusters are not) not accessible from the external world. |
@yuvipanda thanks for this info. Apologies, I should have written |
@yuvipanda just to clarify, if I follow the deployment instructions for the zero-to-jupyterhub-k8s repository I receive an
This automatically sets up a domain name of the form
Should it be possible for me to pass this domain name to let's encrypt via yaml parameters:
Or, is this insufficient information for proving control of the |
Please document how to set up an https entry point for the hub server. Currently the server is accessed by default using http.
The text was updated successfully, but these errors were encountered: