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

user-scheduler: update to use kube-scheduler 1.28, from 1.26 - require k8s 1.24+ #3312

Merged
merged 1 commit into from
Jan 14, 2024

Conversation

consideRatio
Copy link
Member

@consideRatio consideRatio commented Jan 9, 2024

Breaking because we introduce an assumption of k8s 1.24+.

@consideRatio consideRatio force-pushed the pr/test-upgrade-kube-scheduler branch 7 times, most recently from b00fd64 to be5c80d Compare January 10, 2024 14:56
@consideRatio consideRatio changed the title user-scheduler: update to use kube-scheduler 1.28, from 1.26 user-scheduler: update to use kube-scheduler 1.28, from 1.26, requires k8s 1.24+ Jan 10, 2024
@consideRatio consideRatio force-pushed the pr/test-upgrade-kube-scheduler branch from be5c80d to f84f085 Compare January 11, 2024 09:02
@consideRatio consideRatio changed the title user-scheduler: update to use kube-scheduler 1.28, from 1.26, requires k8s 1.24+ user-scheduler: update to use kube-scheduler 1.28, from 1.26 - require k8s 1.24+ Jan 11, 2024
@consideRatio consideRatio marked this pull request as ready for review January 11, 2024 09:06
@manics manics closed this Jan 12, 2024
@manics manics reopened this Jan 12, 2024
@consideRatio consideRatio force-pushed the pr/test-upgrade-kube-scheduler branch from 0667786 to ec8e3e8 Compare January 12, 2024 21:08
@consideRatio
Copy link
Member Author

consideRatio commented Jan 12, 2024

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.

@manics manics merged commit 30a68f1 into jupyterhub:main Jan 14, 2024
12 checks passed
consideRatio pushed a commit to jupyterhub/helm-chart that referenced this pull request Jan 14, 2024
jupyterhub/zero-to-jupyterhub-k8s#3312 Merge pull request #3312 from consideRatio/pr/test-upgrade-kube-scheduler
consideRatio added a commit that referenced this pull request Mar 20, 2024
…be-scheduler"

This reverts commit 30a68f1, reversing
changes made to fe1251c.
consideRatio added a commit that referenced this pull request Mar 20, 2024
…be-scheduler"

This reverts commit 30a68f1, reversing
changes made to fe1251c.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

In Oct 2023 - drop support for k8s 1.23
2 participants