Bump k8s.io deps to v0.26.0

[lucacome]

Updates k8s.io dependencies from v0.25.4 to v0.26.0.

It also updates ROOTDIR in the Makefile to remove the trailing / that was causing some commands (like make verify-vendor) to fail, at least on Mac

[k8s-ci-robot]

Hi @lucacome. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[estesp]

Looks like the updated k8s sets implementation now uses Go generics; our use of string sets is now deprecated, so the linter is failing:

Check failure on line 93 in pkg/cri/server/bandwidth/linux.go

[dcantah]

Do we want to draft here until we figure out the Go version situation/review #7813?

[mikebrow]

/ok-to-test

[thaJeztah]

Looks like the breaking change was introduced in kubernetes/kubernetes#112258. Reading that PRs description, that was not a real "requirement", other than making the code slightly more self-descriptive; I wonder if it should be (temporarily) reverted until go1.18 is no longer widely used.

/cc @liggitt

[k8s-ci-robot]

@thaJeztah: GitHub didn't allow me to request PR reviews from the following users: liggitt.

Note that only containerd members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

Looks like the breaking change was introduced in kubernetes/kubernetes#112258. Reading that PRs description, that was not a real "requirement", other than making the code slightly more self-descriptive; I wonder if it should be (temporarily) reverted until go1.18 is no longer widely used.

/cc @liggitt

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[liggitt]

I wonder if it should be (temporarily) reverted until go1.18 is no longer widely used.

go1.18 goes out of support in ~Feb 2023 with the release of go1.20, so use of go 1.19 is reasonable to require in 1.26

[lucacome]

Superseded by #8131