-
Notifications
You must be signed in to change notification settings - Fork 813
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
user-scheduler: update to use kube-scheduler 1.28, from 1.26 - require k8s 1.24+ #3312
user-scheduler: update to use kube-scheduler 1.28, from 1.26 - require k8s 1.24+ #3312
Conversation
b00fd64
to
be5c80d
Compare
be5c80d
to
f84f085
Compare
0667786
to
ec8e3e8
Compare
It appears that CircleCI behaves differently from GitHub actions. CircleCI seem to test the state of the branch, while GitHub tests the state of the PR if merged - so when we close/re-opened github actions started testing with #3313 that had been merged into main since this branch was created, while CircleCI didn't. The feature to merge first and test later is requested in https://ideas.circleci.com/cloud-feature-requests/p/show-test-results-for-prospective-merge-of-a-github-pr, where the resolution was to use a orb that now seems archived and possibly deprecated - see https://circleci.com/developer/orbs/orb/circleci/build-tools#commands-merge-with-parent. Anyhow, tests are now passing after a rebase. |
jupyterhub/zero-to-jupyterhub-k8s#3312 Merge pull request #3312 from consideRatio/pr/test-upgrade-kube-scheduler
Breaking because we introduce an assumption of k8s 1.24+.