[release-4.17] OCPBUGS-43807: Revendor to a patched k/k with our prefer-local-DNS hack

[openshift-cherrypick-robot]

This is an automated cherry-pick of #638

/assign danwinship

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-43764 has been cloned as Jira Issue OCPBUGS-43807. Will retitle bug to link to clone.
/retitle [release-4.17] OCPBUGS-43807: Revendor to a patched k/k with our prefer-local-DNS hack

In response to this:

This is an automated cherry-pick of #638

/assign danwinship

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]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-43807, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-43764 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

In response to this:

This is an automated cherry-pick of #638

/assign danwinship

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
/lgtm
/approve
/label backport-risk-assessed

[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
/lgtm
/approve
/label backport-risk-assessed

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danwinship, openshift-cherrypick-robot

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]

@openshift-cherrypick-robot: 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/verify	e9d3a47	link	true	/test verify
ci/prow/security	e9d3a47	link	false	/test security
ci/prow/unit	e9d3a47	link	true	/test unit

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.

[asood-rh]

/label cherry-pick-approved

[rtheis]

/jira refresh

[openshift-ci-robot]

@rtheis: This pull request references Jira Issue OCPBUGS-43807, which is invalid:

• expected dependent Jira Issue OCPBUGS-43764 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

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.