You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This guide will help you upgrade from 2.\* to 3.\*.
5
+
6
+
The minimum supported version of Kubernetes is 1.24.
7
+
8
+
## JupyterHub 4 and related hub components
9
+
10
+
Z2JH 3.0.0 upgrades from JupyterHub from 3 to JupyterHub 4.
11
+
There are some minor breaking changes, most notably that XSRF tokens are now used to prevent cross-origin attacks instead of checking the `Referer` header.
12
+
13
+
The database schema is updated to support new features, but this should not affect existing behaviour.
14
+
Z2JH automatically handles the upgrade if you are using sqlite (`hub.db.type = 'sqlite-pvc'`, the default), but it may not be possible to downgrade to older releases after this.
15
+
If you use an external database you need to configure [`hub.db.upgrade`](schema_hub.db.upgrade) to `true` when upgrading.
16
+
17
+
KubeSpawner is upgraded from 4 to 6.
18
+
If you set `KubeSpawner.environment` instead of `singleuser.extraEnv` the symbols `{` and `}` are now used for automatic variable expansion. To retain existing behavior, replace `{` and `}` with `{{` and `}}`.
19
+
20
+
OAuthenticator is upgraded from 15 to 16.
21
+
Previously OAuthenticator would allow any authenticated user by default in most cases.
22
+
This was changed to improve the default security configuration. to retain existing behaviour set `OAuthenticator.allow_all` to `True`.
23
+
24
+
There are major changes to how the `authenticate()` method is implemented.
25
+
If you are overriding OAuthenticator ensure you [read the changelog for 16](https://oauthenticator.readthedocs.io/en/stable/reference/changelog.html#id52https://github.com/jupyterhub/oauthenticator/blob/16.0.4/docs/source/reference/changelog.md).
0 commit comments