Random homedir suffix with helm chart 4.2.0/hub 5.3.0

JupyterHub
1

We currently run JupyterHubs in k8s with helm chart 3.3.5 (JupyterHub 4.1.3) and LTI11Authenticator-1.6.2. The user name and home directory is constructed from a LTI message field containing the mail address, resulting in home directories like jdoe-40ethz-2ech.

Tests with helm chart 4.2.0 (JupyterHub 5.3.0) showed a different behavior: while the user name remains the same, the home directory is created as jdoe-ethz-ch—66dd385c. The old home would be unreachable.

Does anybody know where this suffix comes from? Is there a way to get the old behavior back? Some of our services require a home name which can be derived from the LTI information solely, without a random suffix.

2

Have a look at the upgrade guide for 3 to 4:

The escaping scheme was changed to avoid problems with clashing or overly long resource names. KubeSpawner.slug_scheme: escape should restore the old behaviour.

2 Likes
3

Many thanks to point me in the right direction. Together with singleuser.storage.static.subPath: “{escaped_username}”, everything behaves as before :ok_hand:

2 Likes