Update dependency go modules for k8s v1.26.0

[sunnylovestiramisu]

Ran kubernetes-csi/csi-release-tools go-get-kubernetes.sh -p 1.26.0

Updated Kubernetes dependencies to 1.26.0

[sunnylovestiramisu]

/assign @msau42

[jsafrane]

/release-label-node
/lgmt
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane, sunnylovestiramisu

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jsafrane]

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

[jsafrane]

/release-label-none

[jsafrane]

/release-note-none
?

[jsafrane]

/lgtm
bad day today :-)

[humblec]

@sunnylovestiramisu looks like some dependencies are still with rc tag https://github.com/kubernetes-csi/external-attacher/pull/395/files#diff-33ef32bf6c23acb95f5902d7097b7a1d5128ca061167ec0716715b0b9eeaa5f6L17 or see #396 . considering you have filed PRs in sidecar repos, it would be better to revisit the existing PRs too

[jsafrane]

@humblec good catch, I missed that one.

[humblec]

@humblec good catch, I missed that one.

yw 👍

[sunnylovestiramisu]

I was running the script go-get-kubernetes.sh and this is what the script generated. Do we usually manually update dependencies after running the script? It happened twice already for both 1.26.0-rc and 1.26.0.

[msau42]

I think it's worth digging more into the script to figure out why it's not updating those. We want to get to a state where the script is reliable and doesn't require modifying by hand afterwards