Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Failed to provision JupyterHub: keycloak-address configuration issues on 25.3

Open
#202 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
jupyter-notebook, kubernetes
Domain
devops, infrastructure

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.

Description

Image

Issue Description

When attempting to provision the jupyterhub-pyspark-hdfs-anomaly-detection-taxi-data demo, encountering error:

  • configmap "keycloak-address" not found
Dominant language
Jupyter Notebook
Stars
3
Forks
13
Avg merge
2d 20h
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/demos

All issues in stackabletech/demos

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.