[release-4.17] OCPBUGS-103155: CVE-2026-33814: replace golang.org/x/net with openshift-sustaining fork

[mariocr73]

Same rationale as OCPBUGS-102919 (release-4.16). Builder pinned to Go 1.22 (rhel-9-golang-1.22-openshift-4.17). Uses replace golang.org/x/net => github.com/openshift-sustaining/net v0.35.0-sec.3.

go build/go vet clean; govulncheck confirms GO-2026-4918 no longer reported for ./cmd/azure-disk-csi-driver-operator/....

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@mariocr73: This pull request references Jira Issue OCPBUGS-103155, which is invalid:

• expected dependent Jira Issue OCPBUGS-103371 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Same rationale as OCPBUGS-102919 (release-4.16). Builder pinned to Go 1.22 (rhel-9-golang-1.22-openshift-4.17). Uses replace golang.org/x/net => github.com/openshift-sustaining/net v0.35.0-sec.3.

go build/go vet clean; govulncheck confirms GO-2026-4918 no longer reported for ./cmd/azure-disk-csi-driver-operator/....

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.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: a131c782-6f49-482e-92a5-66b43cee9dfd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[dobsonj]

/lgtm
/approve
/label backport-risk-assessed

[openshift-merge-bot]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-upgrade
/test e2e-azure
/test e2e-azure-csi
/test e2e-azure-file-csi
/test e2e-azure-file-nfs-csi
/test e2e-azure-ovn-upgrade

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dobsonj, mariocr73

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 [dobsonj]

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

[mariocr73]

/retest

[mariocr73]

/retest

[openshift-ci]

@mariocr73: The following tests 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-azure-file-nfs-csi	504c169	link	true	/test e2e-azure-file-nfs-csi
ci/prow/e2e-azure-file-csi	504c169	link	true	/test e2e-azure-file-csi
ci/prow/unit	504c169	link	true	/test unit

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.