Skip to content

docs(juypterhub-keycloak: Improve section about web interface access #249

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jul 16, 2025
Merged

docs(juypterhub-keycloak: Improve section about web interface access #249

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/modules/demos/pages/jupyterhub-keycloak.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -146,9 +146,11 @@ proxy-648bf7f45b-62vqg 1/1 Running 0 56m

----

The `proxy` Pod has an associated `proxy-public` service with a statically-defined port (31095), exposed with type NodePort. The `keycloak` Pod has a Service called `keycloak` with a fixed port (31093) of type NodePort as well.
In order to reach the JupyterHub web interface, navigate to this service.
The `proxy` Pod has an associated `proxy-public` service with a statically-defined port (31095), exposed with type NodePort.
The `keycloak` Pod has a Service called `keycloak` with a fixed port (31093) of type NodePort as well.
The node port IP can be found in the ConfigMap `keycloak-address` (written by the Keycloak Deployment as it starts up).
Both the Keycloak and the JupyterHub web interface can be accessed via this address, on ports 31093 and 31095 respectively.

On Kind this can be any node - not necessarily the one where the proxy Pod is running.
This is due to the way in which Docker networking is used within the cluster.
On other clusters it will be necessary to use the exact Node on which the proxy is running.
Expand Down