Replies: 3 comments
-
Example of web response
|
Beta Was this translation helpful? Give feedback.
0 replies
-
I did attempt to spoof the |
Beta Was this translation helpful? Give feedback.
0 replies
-
I'm closing old discussions in a repo cleanup effort. Feel free to re-open if needed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Wanted to detail a currently manual but good approach for scalably exposing dashboards external to jupyterhub. The motivation for this is the need for a long running, authenticated dashboard behind a custom url. QHub already has much of the foundation for this. Ideally in the future we will provide an extension mechanism to make this process easier and more integrated.
First step is to create a docker image and Kubernetes pod of the given dashboard/web server. In this example we will use the
traefik/whoami
service. This allows us to easily see the http headers (only for an example). Use your own dashboard here.Next define a service that maps to this dashboard.
Finally we us traefik to do all the heavy lifting. There is a middleware using traefik forward auth which provides transparent authentication. In addition it sets the header
X-Forwarded-User
. Traefik will attempt to fetch certificates for any Host that you set. Also we have sticky sessions enabled! This allows for all requests from a given user to go to the same server every time. This allows stateful dashboards to operate properly.Beta Was this translation helpful? Give feedback.
All reactions