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

CI system broken with k8s 1.25 (at least k3s 1.25) #1541

Closed
consideRatio opened this issue Oct 10, 2022 · 1 comment · Fixed by #1544
Closed

CI system broken with k8s 1.25 (at least k3s 1.25) #1541

consideRatio opened this issue Oct 10, 2022 · 1 comment · Fixed by #1544
Labels
ci maintenance Under the hood improvements and fixes

Comments

@consideRatio
Copy link
Member

Without changes to this repo, our CI system has started failing, where a created build pod get stuck in pending state.

I'm quite confident it is because we started using k8s 1.25. Note though that the jupyterhub/action-k3s-helm action is providing us with some bridging tech called cri-dockerd, so I thought maybe we wouldn't end up with issues related to that.

Oldest test failure: https://github.com/jupyterhub/binderhub/actions/runs/3210481910/jobs/5247954722#step:28:106
Most recent test success: https://github.com/jupyterhub/binderhub/actions/runs/2987255039/jobs/4789548250

@consideRatio consideRatio changed the title CI system broken due to external change CI system broken with k8s 1.25 (at least k3s 1.25) Oct 10, 2022
@consideRatio consideRatio added maintenance Under the hood improvements and fixes ci labels Oct 10, 2022
@consideRatio
Copy link
Member Author

I conclude its z2jh as a dependency, with the user scheduler, that doesn't work with k8s 1.25. So the fix is to upgrade to z2jh 2.0.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci maintenance Under the hood improvements and fixes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant