-
Notifications
You must be signed in to change notification settings - Fork 809
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
Kubernetes 1.16 compatibility #1444
Comments
I think jupyterhub/kubespawner#355 is another k8s 1.16 related issue (and fix). |
@betatim right, i think that's exactly the 3rd one i listed. let me link that as well. |
Now merged jupyterhub/kubespawner#356. Maybe it is a temporary fix but it'll get people unblocked and we can make a better fix later. WDYT? |
@betatim Unfortunately, jupyterhub/kubespawner#356 did not solve the issue for me:
|
In #1422 I'm now testing against 1.16 but allowing allow for failures. https://travis-ci.org/jupyterhub/zero-to-jupyterhub-k8s/jobs/599062620 |
jupyterhub/kubespawner#357 is up for people who are having trouble running with kubernetes 1.16 to take over and finish off. I won't get around to pushing it over the finish line. |
Help pushing jupyterhub/kubespawner#357 through the finish line would be appreciated. Note that the current development setup described in CONTRIBUTING.md may make it a plausible to locally develop a functional solution of z2jh+kubespawner+k8s 1.16. I suggest using the To get the test to use a locally developed kubespawner, I suggest to git clone kubespawner into the images/hub folder, and in the images/hub/Dockerfile add some steps where we copy the local kubespawner repo along with local changes and install it with |
Quick and dirty way:
And test as normal (or push to GitHub as a temporary branch and let travis test it for you) |
@clkao, all these issues are now being addressed, mostly in #1483:
|
It appears there are several issues with running z2jh on kubernetes 1.16, running the latest master with kind:
scheduling.userScheduler.enabled: true
causing user pod to stuck in Pending state, without any eventsingleuser.events: true
causing launch failures, as events seem not to be what EventReflector is expecting: (kubespawner stopped working after kubernetes upgrade from 1.15 to 1.16 kubespawner#354)I haven't looked further but each of them should probably be of its own issue
The text was updated successfully, but these errors were encountered: