CONSOLE-5134: Update to Go 1.25, K8s 1.35, and Helm 3.20

[webbnh]

OpenShift 4.22 is built on Kubernetes 1.35. This change updates Console's dependency on k8s.io/api to match that; and, it updates the dependency on helm.sh/helm/v3 to v3.20 to match that.

This requires updating the Go dependency to 1.25.

And, these three upgrades pull in updates to a dozen other direct dependencies and 30+ indirect dependencies.

So, while this change intentionally targets only the go.mod file, the go.sum file and about 2000 files in the vendor/ subdirectory are changed as well.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[webbnh]

/test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: webbnh
Once this PR has been reviewed and has the lgtm label, please assign rhamilto 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

[logonoff]

Don't forget to also update the go version requirement in the readme

[logonoff]

/test all

[webbnh]

/test all

[openshift-ci-robot]

@webbnh: This pull request explicitly references no jira issue.

Details

In response to this:

This change updates the dependency on helm.sh/helm/v3 to v3.20.

This requires updating the Go dependency to 1.25.

And, these two upgrades pull in updates to a dozen other direct dependencies and 30+ indirect dependencies.

So, this change targets only the go.mod file, and, of course, the go.sum file, and, of course, about 2000 files in the vendor/ subdirectory.

Please let me know if I've gone about this incorrectly. Thanks!

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 openshift-eng/jira-lifecycle-plugin repository.

[logonoff]

Makes sense to me but I think we should have a jira for this

[logonoff]

/label px-approved
/label docs-approved

[webbnh]

we should have a jira for this

OK...which "space" should I open it in (HELM, CONSOLE, something else?), and what should it say?

The Helm API should be updated when the Kubernetes API is updated, and the K8s API should presumably be updated whenever the version of it used by OpenShift is updated. (OpenShift, AIUI, is now on K8s 1.35; Console appears to have been updated to K8s 1.34 in #15926, although the description for it doesn't mention the update).

[logonoff]

OK...which "space" should I open it in (HELM, CONSOLE, something else?), and what should it say?

I think either is fine... it's been traditionally in OCPBUGS or CONSOLE depending on the context of the upgrade (feel free to check the git blame). You can write something along the lines of "Bump k8s and helm version", and if you want to be extra fancy about it, you could link that ticket as a "blocker" for the feature you're trying to implement with the new helm version :)

[openshift-ci-robot]

@webbnh: This pull request references CONSOLE-5134 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

OpenShift 4.22 is built on Kubernetes 1.35. This change updates Console's dependency on k8s.io/api to match that; and, it updates the dependency on helm.sh/helm/v3 to v3.20 to match that.

This requires updating the Go dependency to 1.25.

And, these three upgrades pull in updates to a dozen other direct dependencies and 30+ indirect dependencies.

So, while this change intentionally targets only the go.mod file, the go.sum file and about 2000 files in the vendor/ subdirectory are changed as well.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@webbnh: This pull request references CONSOLE-5134 which is a valid jira issue.

Details

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[sowmya-sl]

/verified by @sowmya-sl

[openshift-ci-robot]

@sowmya-sl: This PR has been marked as verified by @sowmya-sl.

Details

In response to this:

/verified by @sowmya-sl

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 openshift-eng/jira-lifecycle-plugin repository.

[webbnh]

/retest

[webbnh]

/retest

[openshift-ci]

@webbnh: 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
ci/prow/e2e-gcp-console	acb6451	link	true	/test e2e-gcp-console

Full PR test history. Your PR dashboard.

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.

[webbnh]

/retest