Failing 1.35 e2e tests

[Edwinhr716]

What would you like to be cleaned: Ever since we updated our tests to use 1.35, they have been failing.

Why is this needed: Blocking new PRs from being merged

[Edwinhr716]

Sample failure https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_lws/749/pull-lws-test-e2e-main-1-35/2018381671195217920

@yankay did we miss anything when we upgraded the dependencies to 0.35 in #741?

[yankay]

I'll take a look as soon as I have a time slice.

[yankay]

This issue appears to be related to a bug in Kubernetes 1.35, and may require waiting for a Kubernetes patch release to be resolved.

[Edwinhr716]

Do you have any more details? I'm fine with making 1.35 e2e tests optional, but wondering why JobSet for example is not running into issues. Could be the controller-runtime version since they are still in 0.22.4 kubernetes-sigs/jobset#1146

[kannon92]

kubernetes/kubernetes#136774

Looks like to be a regression in statefulset.

[yankay]

Do you have any more details? I'm fine with making 1.35 e2e tests optional, but wondering why JobSet for example is not running into issues. Could be the controller-runtime version since they are still in 0.22.4 kubernetes-sigs/jobset#1146

It appears to be a regression in StatefulSet. I've rolled back the controller-runtime version to 0.22.4, and the issue still persists.