I have a running docker-based hub infrastructure where I’m using
Authenticator.refresh_user to refresh/regenerate infrastructure API keys that are then passed (live) to the spawned jupyter instances via per-user filesystem mounts (being updated/refreshed by the hub before the keys expire for the end-user, every few hours - with the user automatically pulling in the updates via boto RefreshableCredential overrides)
I’m attempting to build up a similar key refreshing environment in kubernetes (z2h). My issue is I’m unsure how to approach getting the continously updated (hub) keys to the (running) spawned jupyter pods.
Searching through the forum, one solution that struck me was to use the spawned-instance’s Hub API key to have the instance request updated key from the hub (found from this post JupyterLab extension to get info from hub api )
Using that approach I’m wondering if I would have to extend the hub’s REST API because the updated keys are currently being stored in the
auth_state database and I don’t see any REST calls for access that.
Has anyone else addressed having the hub send key updates out to running spawned instances or have any other ideas on how to approach this?