---
# System prepended metadata

title: binderhub-service meet 2023-06-21

---


Meeting with Erik, Georgiana, and Yuvi

Meeting goals:
- to sync status about where we are
- knowing what to do next
- devseed on frontend, and path forward

## Status
- DONE: config passthrough
    Resolved by https://github.com/2i2c-org/binderhub-service/pull/18
- Container registry credentials, PR open (https://github.com/2i2c-org/binderhub-service/pull/36), Erik todo
- basehub install example
    - binderhub-service is added as an opt-in chart dependency for basehub
    - that is trialed to function in a demo-deployment
    - step 1 is to just get binderhub-service started but not coupled with jupyterhub
    - step 2 is to couple with jupyterhub in some ways
        - auth: such as making requests to build only allowed by jupyterhub authenticated users
        - UI: https://github.com/yuvipanda/prototype-kubespawner-dynamic-building-ui
        - kubespawner: https://github.com/jupyterhub/kubespawner/pull/735#issuecomment-1600903593
- document binderhub-service to start next to a jupyterhub and authorize requests based on jupyterhub users

## Work needs to be done in

1. 2i2c-org/infrastructure
- 2i2c-org/binderhub-service
- yuvipanda/prototype-kubespawner-dynamic-building-ui
- jupyterhub/binderhub, [build-request PR](https://github.com/jupyterhub/binderhub/pull/1647)
- jupyterhub/kubespawner, [free form input PR](https://github.com/jupyterhub/kubespawner/pull/735)


## Decisions

- We get basehub to use z2jh 3.0.0-beta.1
- We need the kubespawner PR, so we will maintain our own branch of that PR, rebased on kubespawner 6 used in z2jh 3.0.0-beta.1


## Work item and priority

- [ ] Min/Simon: binderhub PR reviewed (Erik will ask)
- [x] Erik: Container registry credentials, PR open (https://github.com/2i2c-org/binderhub-service/pull/36)
- [x] Georgiana: binderhub-service, rebase the PR branch
- [x] Erik: basehub to depend on z2jh 3.0.0-beta.1
- Deploy demo basehub with integration to binderhub-service
    - [x] Georgiana: binderhub-service is deployed separately to jupyterhub, as an opt-in dependency for basehub
    - ------ Erik/Georgiana/Yuvi discussed this as a checkpoint -----
    - 2i2c-org/infrastructure supports providing a container registry via terraform for binderhub-service to work against
    - binderhub-service is authorizing build requests based on jupyterhub identity
    - jupyterhub is configured with prototype-kubespawner-dynamic-building-ui
    - jupyterhub is launching built image (requires kubespawner PR)
- Erik: CI work in binderhub-service
- Documentation of binderhub-service
- Yuvi: coordination work with devseed
- Yuvi: will writeup a Q3 goal


## Not yet mentioned

prototype ui: frontend work
prototype ui: tests, release automation, changelog, autoformatting setup etc
    recommendation to look at jupyterhub/jupyterhub-python-repo-template
frontend work in prototype ui
ci work in binderhub-service
binderhub 1.0.0
