stackabletech / stackabletech/demos
Failed to provision JupyterHub: keycloak-address configuration issues on 25.3
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 3
- Forks
- 13
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 2
Description
Issue Description
When attempting to provision the jupyterhub-pyspark-hdfs-anomaly-detection-taxi-data demo, encountering error:
- configmap "keycloak-address" not found
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing provisioning for the jupyterhub-pyspark-hdfs-anomaly-detection-taxi-data demo on version 25.3 and inspect how the keycloak-address ConfigMap is expected to be created. Trace the provisioning output around the missing ConfigMap and compare it with the demo configuration. Done means the demo provisions successfully without the “configmap keycloak-address not found” error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100