UPSTREAM: <drop>: Bump golang.org/x/net to v0.23.0

[flavianmissi]

./hack/pin-dependency.sh golang.org/x/net v0.23.0
./hack/update-vendor.sh

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[openshift-ci-robot]

@flavianmissi: This pull request references Jira Issue OCPBUGS-30844, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead
• expected Jira Issue OCPBUGS-30844 to depend on a bug targeting a version in 4.15.0, 4.15.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

In response to this:

./hack/pin-dependency.sh golang.org/x/net v0.23.0
./hack/update-vendor.sh

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

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]

@flavianmissi: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 2ceeb91|UPSTREAM: : Bump golang.org/x/net to v0.23.0: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

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

[openshift-merge-robot]

PR needs rebase.

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.

[openshift-ci]

@flavianmissi: 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-gcp	2ceeb91	link	true	/test e2e-gcp
ci/prow/k8s-e2e-gcp-serial	2ceeb91	link	true	/test k8s-e2e-gcp-serial
ci/prow/unit	2ceeb91	link	true	/test unit
ci/prow/k8s-e2e-gcp-ovn	2ceeb91	link	true	/test k8s-e2e-gcp-ovn
ci/prow/e2e-agnostic-ovn-cmd	2ceeb91	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/e2e-gcp-ovn-upgrade	2ceeb91	link	true	/test e2e-gcp-ovn-upgrade

Full PR test history. Your PR dashboard.

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

[openshift-ci-robot]

@flavianmissi: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

./hack/pin-dependency.sh golang.org/x/net v0.23.0
./hack/update-vendor.sh

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

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.

[flavianmissi]

upstream has already merged this bump on 1.27. since we've landed the openshift-priv changes already, we don't need this PR. next time we bump this repo with upstream kube we'll get the x/net bump and everything will be right again.
/close

[openshift-ci]

@flavianmissi: Closed this PR.

In response to this:

upstream has already merged this bump on 1.27. since we've landed the openshift-priv changes already, we don't need this PR. next time we bump this repo with upstream kube we'll get the x/net bump and everything will be right again.
/close

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.