Bump go version to 1.26 to match the main kubernetes repo

[tetianakh]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Bumps go version to 1.26 which is already used in the main kubernetes repo.
Also, the change fixes some bugs that were picked up by strict vet checks introduced in 1.26

Bump go version to 1.26

[k8s-ci-robot]

Hi @tetianakh. Thanks for your PR.

I'm waiting for a kubernetes 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.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

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.

Details

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-sigs/prow repository.

[x13n]

/ok-to-test
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: tetianakh, x13n
Once this PR has been reviewed and has the lgtm label, please assign jackfrancis for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[adrianmoisey]

/cc jackfrancis

[k8s-ci-robot]

New changes are detected. LGTM label has been removed.

[tetianakh]

@adrianmoisey would you be open to sponsoring my membership in the k8s org?

[adrianmoisey]

@adrianmoisey would you be open to sponsoring my membership in the k8s org?

Taking a look at https://github.com/kubernetes/community/blob/main/community-membership.md#member

I see:

Members are continuously active contributors in the community

This is the first contribution I've seen, so I can't sponsor your membership, sorry.

[tetianakh]

@adrianmoisey would you be open to sponsoring my membership in the k8s org?

Taking a look at https://github.com/kubernetes/community/blob/main/community-membership.md#member

I see:

Members are continuously active contributors in the community

This is the first contribution I've seen, so I can't sponsor your membership, sorry.

I have made the following contributions:

• List managed instances #9213
• Add GetMigIsStable and refactor MigInfoProvider #9291
• Initialize sharedCSIManager in scheduler framework #9012

And I have 2 that are still open, not counting this one:

• Fast-track evaluation path for host-scoped affinity/anti-affinity kubernetes#138198 (open)
• Track node removal latency for empty and non-empty nodes #9377 (open)

Until now, the automation selected reviewers and approvers from my company, so I am really stuck trying to get a second sponsor.

[adrianmoisey]

The guidelines are pretty clear:

Authoring or reviewing PRs on GitHub, with at least one merged PR. NOTE: The PR(s) must demonstrate an ongoing and active commitment. A few examples include:

• A single KEP that has taken several weeks of driving consensus
• A larger number of smaller PRs over several weeks to months
• A smaller number of complex or technical PRs that required working with community members to resolve an issue (e.g. regressions, bugs fixes etc)

I know it's up for interpretation, but, I don't believe that 3 merged PR and 2 open PRs satisfies: "a larger number of smaller PRs over several weeks to months"

[tetianakh]

The guidelines are pretty clear:

Authoring or reviewing PRs on GitHub, with at least one merged PR. NOTE: The PR(s) must demonstrate an ongoing and active commitment. A few examples include:

• A single KEP that has taken several weeks of driving consensus
• A larger number of smaller PRs over several weeks to months
• A smaller number of complex or technical PRs that required working with community members to resolve an issue (e.g. regressions, bugs fixes etc)

I know it's up for interpretation, but, I don't believe that 3 merged PR and 2 open PRs satisfies: "a larger number of smaller PRs over several weeks to months"

Ok, thank you for taking the time to consider this. I'll keep merging then!

[jackfrancis]

/retest

[tetianakh]

/retest

[k8s-ci-robot]

@tetianakh: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-autoscaling-e2e-gci-gce-ca-test	61cf235	link	false	/test pull-autoscaling-e2e-gci-gce-ca-test

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

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-sigs/prow repository. I understand the commands that are listed here.