Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release planning for 6.1.0 #767

Closed
consideRatio opened this issue Aug 22, 2023 · 9 comments · Fixed by #768
Closed

Release planning for 6.1.0 #767

consideRatio opened this issue Aug 22, 2023 · 9 comments · Fixed by #768

Comments

@consideRatio
Copy link
Member

consideRatio commented Aug 22, 2023

KubeSpawner would benefit greatly from a release with #742 in it, what I think was a regression from previous major versions of KubeSpawner. Z2JH 3.0.0 - 3.0.3 users are affected by it. The consequences of this bug is that user pods can be left running in k8s while JupyterHub thinks the servers are stopped, and this can incurr significant cloud costs. Users with a stranded server can still re-start it via JupyterHub though.

To make this release, we should also include notes on how users can cleanup such stranded servers intelligently. @minrk has made a script that inspects k8s resources and the jupyterhub state to help figure out what user servers should be considered for cleanup.

Todo

Todo related to unlisted_choice

Todo considered outside the scope of this release

@yuvipanda

This comment was marked as resolved.

@consideRatio

This comment was marked as resolved.

@consideRatio

This comment was marked as resolved.

@consideRatio

This comment was marked as resolved.

@GeorgianaElena

This comment was marked as resolved.

@consideRatio

This comment was marked as resolved.

@consideRatio

This comment was marked as resolved.

@consideRatio

This comment was marked as resolved.

@yuvipanda

This comment was marked as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants