Closed consideRatio closed 2 months ago
I figure we should adopt a policy like in z2jh, where we would then drop support for k8s 1.26 in June 2024 (https://github.com/jupyterhub/zero-to-jupyterhub-k8s/issues/3321).
So, to drop now is quite reasonable. The motivation to get this done now was observing a k8s 1.24 failure in our test suite.
I figure we should adopt a policy like in z2jh, where we would then drop support for k8s 1.26 in June 2024 (https://github.com/jupyterhub/zero-to-jupyterhub-k8s/issues/3321).
So, to drop now is quite reasonable. The motivation to get this done now was observing a k8s 1.24 failure in our test suite.