Skip to content

Commit

Permalink
docs: bumping kube-scheduler by itself isn't breaking
Browse files Browse the repository at this point in the history
It was that it required a minimum k8s version that introduced the
breakign change associated with bumping kube-scheduler.
  • Loading branch information
consideRatio committed Sep 23, 2024
1 parent c8093e3 commit 38e583f
Showing 1 changed file with 0 additions and 1 deletion.
1 change: 0 additions & 1 deletion docs/source/changelog.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,6 @@ changes in pull requests], this list should be updated.

- Update jupyterhub from 4.1.6 to 5.1.0 [#3405](https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/3405), [#3416](https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/3416), [#3425](https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/3425), [#3472](https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/3472)
- Drop support for k8s 1.23-1.27, require k8s 1.28+ [#3312](https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/3312), [#3403](https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/3403), [#3319](https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/3319), [#3508](https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/3508)
- user-scheduler: update to use kube-scheduler 1.28, from 1.26 [#3312](https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/3312)

## 3.3

Expand Down

0 comments on commit 38e583f

Please sign in to comment.