k8s 1.16 compability - bump kube-scheduler, kubespawner, kubernetes python client, oauthenticator#1483
Merged
consideRatio merged 8 commits intojupyterhub:masterfrom Nov 28, 2019
Merged
Conversation
consideRatio
changed the title
consideRatio
changed the title
consideRatio
changed the title
Member
|
Presumably when 1.16 is fixed you can remove zero-to-jupyterhub-k8s/.travis.yml Line 59 in 9a26b4c |
|
This pull request has been mentioned on Jupyter Community Forum. There might be relevant details there: https://discourse.jupyter.org/t/binder-jupyterhub-activity-round-up-week-1/2704/1 |
consideRatio
force-pushed
the
prep-k8s-1.16
branch
from
d656726 to
adbf140
Compare
|
It'd be nice if in the meantime the kubeVersion was modified to |
This was referenced Nov 26, 2019
This was required for the pods to not get stuck in pending on k8s 1.16, I'm not sure what changes but hey we were using a k8s 1.11 user-scheduler image along with k8s 1.16 after all...
consideRatio
force-pushed
the
prep-k8s-1.16
branch
from
adbf140 to
3077204
Compare
consideRatio
changed the title
Member
Author
|
Hmmmm... Trying and failing to pull image? |
Member
Author
|
The unexpected path stuff I experienced in the CI system relates to |
Closed
consideRatio
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If I don't bump kube-scheduler, I note that the scheduler stop working in k8s 1.16. I'm not sure why. Anyhow, I bump various versions at the moment to see what works and doesn't work. We are bumping from kube-scheduler v1.11.2 in use by user-scheduler, which is just a configured kube-scheduler. These are the available images.
Perhaps there are more things needed to be done, but I think all known issues are now addressed.
Closes #1444 entirely, see: #1444 (comment).