GCE: E2E test - supplied static IP for internal LBs

[nicksardo]

ILB test will now reserve an RFC 1918 address within the subnetwork and set the loadBalancerIP field of the K8s service. The test will know the service controller successfully syncs after the loadbalancer's external IP updates to said address.

Release note:

NONE

[k8s-github-robot]

This PR hasn't been active in 61 days. It will be closed in 28 days (Dec 31, 2017).

cc @nicksardo

You can add 'keep-open' label to prevent this from happening, or add a comment to keep it open another 90 days

[nicksardo]

/assign @bowei
/unassign nicksardo

[nicksardo]

/retest
/sig network
/area platform/gce

[nicksardo]

/assign @MrHohn

[MrHohn]

/lgtm

[nicksardo]

/assign @vishh

[nicksardo]

/retest

[nicksardo]

/test pull-kubernetes-e2e-gke

[MrHohn]

/lgtm

The gke pull job seems to be failing on many PRs.

[nicksardo]

/test pull-kubernetes-e2e-gke

[MrHohn]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: MrHohn, nicksardo
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: vishh

If they are not already assigned, you can assign the PR to them by writing /assign @vishh in a comment when ready.

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:

• cluster/gce/OWNERS
• hack/OWNERS
• test/OWNERS [MrHohn]

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

[k8s-ci-robot]

@nicksardo: The following tests failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
pull-kubernetes-e2e-gce-bazel	117ac61	link	/test pull-kubernetes-e2e-gce-bazel
pull-kubernetes-unit	7bbe63fe6a0f7a89f324b20b45b6563a7aac1213	link	/test pull-kubernetes-unit

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

[k8s-ci-robot]

New changes are detected. LGTM label has been removed.

[nicksardo]

Will need to add a deletion for internal addresses in https://github.com/kubernetes/kubernetes/blob/e49e3baa832986ba57e9d155333a9d49b0e13b32/cluster/gce/util.sh
Otherwise, orphaned addresses will cause orphaned subnets/networks.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.