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
Trial upgrade a staging hub involving google auth via cilogon
The text was updated successfully, but these errors were encountered:
consideRatio
changed the title
[EPIC] Upgrade z2jh to v4 with jupyterhub v5, kubespawner v7, and oauthenticator v17
[EPIC] (DRAFT) Upgrade z2jh to v4 with jupyterhub v5, kubespawner v7, and oauthenticator v17
Oct 2, 2024
consideRatio
changed the title
[EPIC] (DRAFT) Upgrade z2jh to v4 with jupyterhub v5, kubespawner v7, and oauthenticator v17
[EPIC] Upgrade z2jh to v4 with jupyterhub v5, kubespawner v7, and oauthenticator v17
Nov 13, 2024
consideRatio
changed the title
[EPIC] Upgrade z2jh to v4 with jupyterhub v5, kubespawner v7, and oauthenticator v17
Trial upgrade z2jh to v4 with jupyterhub v5, kubespawner v7, and oauthenticator v17
Nov 13, 2024
This was completed by #4979 where z2jh 4.0.0-beta.4 was tested, and misc issues detected has been fixed upstream already for z2jh 4.0.0 which is now out.
This EPIC tracks trialing upgrading to z2jh 4.0.0.
subPath: "{escaped_username}"
instead ofsubPath: "{username}"
Part of Testing upgrade from jupyterhub 3.3.7 to 4.0.0-beta.4 #4979.
The text was updated successfully, but these errors were encountered: