[release-4.7] Bug 2043804: UPSTREAM 107564: kube-apiserver integration test: allow IPs with leading zeros on the API

[openshift-cherrypick-robot]

This is an automated cherry-pick of #1124

/assign aojea

[openshift-ci-robot]

@openshift-cherrypick-robot: the contents of this pull request could be automatically validated.

The following commits are valid:

• 75eb6dc|UPSTREAM: 107564: test API allow IPs with leading zeros: the upstream PR kubernetes/kubernetes#107564 has merged

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

[openshift-ci]

@openshift-cherrypick-robot: Bugzilla bug 2042493 has been cloned as Bugzilla bug 2043804. Retitling PR to link against new bug.
/retitle [release-4.7] Bug 2043804: UPSTREAM 107564: kube-apiserver integration test: allow IPs with leading zeros on the API

In response to this:

[release-4.7] Bug 2042493: UPSTREAM 107564: kube-apiserver integration test: allow IPs with leading zeros on the API

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]

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2043804, which is invalid:

• expected dependent Bugzilla bug 2042493 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED instead
• expected dependent Bugzilla bug 2042493 to target a release in 4.8.0, 4.8.z, but it targets "4.10.0" instead

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

In response to this:

[release-4.7] Bug 2043804: UPSTREAM 107564: kube-apiserver integration test: allow IPs with leading zeros on the API

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
To complete the pull request process, please assign sttts after the PR has been reviewed.
You can assign the PR to them by writing /assign @sttts in a comment when ready.

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-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	75eb6dc	link	true	/test verify
ci/prow/e2e-azure	75eb6dc	link	true	/test e2e-azure
ci/prow/e2e-agnostic-cmd	75eb6dc	link	true	/test e2e-agnostic-cmd
ci/prow/e2e-aws-jenkins	75eb6dc	link	true	/test e2e-aws-jenkins
ci/prow/e2e-aws-ovn	75eb6dc	link	true	/test e2e-aws-ovn
ci/prow/integration	75eb6dc	link	true	/test integration

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.

[sosiouxme]

handled in parallel PR