🌱 Bump k8s.io/* deps to v0.35.0

[kannon92]

Update k8s dependencies to 0.35.

[sbueringer]

Thx!

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Details

Git tree hash: ba2c3a883e12b9cc3938ce521bb6c51ef98ad01a

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kannon92, sbueringer

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [sbueringer]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kannon92]

@sbueringer I was doing this as I hit some issues with my k8s 1.35 bump for JobSet. kubernetes-sigs/jobset#1105

Do you think a release of controller runtime would solve this problem?

error:

/home/prow/go/src/sigs.k8s.io/jobset/test/integration/controller/suite_test.go:57
  STEP: bootstrapping test environment @ 12/18/25 03:12:40.027
  2025-12-18T03:12:40Z	DEBUG	controller-runtime.test-env	starting control plane
  2025-12-18T03:12:40Z	ERROR	controller-runtime.test-env	unable to start the controlplane	{"tries": 0, "error": "exec: \"etcd\": executable file not found in $PATH"}
  sigs.k8s.io/controller-runtime/pkg/envtest.(*Environment).startControlPlane
  	/home/prow/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.22.4/pkg/envtest/server.go:391
  sigs.k8s.io/controller-runtime/pkg/envtest.(*Environment).Start
  	/home/prow/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.22.4/pkg/envtest/server.go:304
  sigs.k8s.io/jobset/test/integration/controller.init.func3
  	/home/prow/go/src/sigs.k8s.io/jobset/test/integration/controller/suite_test.go:70
  github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3
  	/home/prow/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.27.3/internal/node.go:524
  github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3
  	/home/prow/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.27.3/internal/suite.go:942
  2025-12-18T03:12:40Z	ERROR	controller-runtime.test-env	unable to start the controlplane	{"tries": 1, "error": "exec: \"etcd\": executable file not found in $PATH"}

[sbueringer]

No. I think your problem is unrelated.

I saw a similar issue a few times in Cluster API jobs and the problem was that setup-envtest failed to download envtest binaries from GitHub release attachments because GitHub itself had issues.

EDIT: I'll continue the conversation on your PR

ETA for the next CR release is ~ early January (depends on maintainer availability/PTO)