ci: test failures in main - hub launched pods pending - related to k3s 1.27?

[consideRatio]

We have tests failing in the main branch, and I don't understand why. It seems that pods get stuck pending. I'm not sure why, but I think k3s 1.27 being released is related. We see a test failure in kubespawner as well, but I'm not sure if that is related.

See the test failures in the main branch started april at least after 26 11.30 AM GMT+2.

Note that we don't have test failures in z2jh, or kubespawner against the k3s 1.27.

[consideRatio]

I've understood what this is about now. Its the jupyterhub chart's user-scheduler in z2jh 2.0.0 that isn't compatible with k8s 1.27, which makes the build pods get stuck in pending as they have been configured to use the user-scheduler.

It is compatible with k8s 1.27 in the development release of z2jh though.