OCPBUGS-43764: Revendor to a patched k/k with our prefer-local-DNS hack

[danwinship]

Apparently IBM was relying on this behavior in the standalone kube-proxy image.

(This also updates from k8s v1.30.3 to v1.30.5, which pulls in some irrelevant changes, and probably I should have just stuck with 1.30.3 to keep it simple but whatever. Anyway, the relevant change is in vendor/k8s.io/kubernetes/pkg/proxy/iptables/proxier.go.)

The replace stuff in go.mod is just taken from the 4.16 branch. I had simplified things when rebasing to 1.30 for 4.17 because we weren't going to be keeping local patches any more, but now we are again, so...

[openshift-ci-robot]

@danwinship: This pull request references Jira Issue OCPBUGS-43764, which is invalid:

• expected the bug to target the "4.18.0" version, but no target version was set

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:

Apparently IBM was relying on this behavior in the standalone kube-proxy image.

(This also updates from k8s v1.30.3 to v1.30.5, which pulls in some irrelevant changes, and probably I should have just stuck with 1.30.3 to keep it simple but whatever. Anyway, the relevant change is in vendor/k8s.io/kubernetes/pkg/proxy/iptables/proxier.go.)

The replace stuff in go.mod is just taken from the 4.16 branch. I had simplified things when rebasing to 1.30 for 4.17 because we weren't going to be keeping local patches any more, but now we are again, so...

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.

[danwinship]

/jira refresh

[openshift-ci-robot]

@danwinship: This pull request references Jira Issue OCPBUGS-43764, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.0) matches configured target version for branch (4.18.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @zhaozhanqi

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.

[danwinship]

/override ci/prow/unit
/override ci/prow/verify

openshift/sdn CI is broken on master

[openshift-ci]

@danwinship: Overrode contexts on behalf of danwinship: ci/prow/unit, ci/prow/verify

In response to this:

/override ci/prow/unit
/override ci/prow/verify

openshift/sdn CI is broken on master

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.

[openshift-ci]

@danwinship: 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/security	44c7965	link	false	/test security

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

[kyrtapz]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danwinship, kyrtapz

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

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

[openshift-ci-robot]

@danwinship: Jira Issue OCPBUGS-43764: All pull requests linked via external trackers have merged:

• openshift/sdn#638

Jira Issue OCPBUGS-43764 has been moved to the MODIFIED state.

In response to this:

Apparently IBM was relying on this behavior in the standalone kube-proxy image.

(This also updates from k8s v1.30.3 to v1.30.5, which pulls in some irrelevant changes, and probably I should have just stuck with 1.30.3 to keep it simple but whatever. Anyway, the relevant change is in vendor/k8s.io/kubernetes/pkg/proxy/iptables/proxier.go.)

The replace stuff in go.mod is just taken from the 4.16 branch. I had simplified things when rebasing to 1.30 for 4.17 because we weren't going to be keeping local patches any more, but now we are again, so...

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.

[danwinship]

/cherry-pick release-4.17

[openshift-cherrypick-robot]

@danwinship: new pull request created: #640

In response to this:

/cherry-pick release-4.17

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.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: kube-proxy
This PR has been included in build kube-proxy-container-v4.18.0-202410241142.p0.g18a57d7.assembly.stream.el9.
All builds following this will include this PR.