Fail ingress creation if specified staticIP name does not exist

[prameshj]

The current behavior is to create a different staticIP and use that in the forwarding rule. Once the user-specified ip becomes available, the forwarding rule ip will flip to using that, causing some downtime.

With this change, ingress creation will fail and retry until the user-specified IP has been created out of band.

@spencerhance

[spencerhance]

lgtm

[prameshj]

/assign @bowei

[bowei]

is it possible to dig around to see what the context was for the original behavior/

git log -S "doesn't translate to an existing global static IP"
git log -G "doesn't translate to an existing global static IP"

[prameshj]

git log -S "doesn't translate to an existing global static IP"

This was introduced in 3ee943d and has not changed much other than being moved to a different file in db96b94

The comment in the original change states:

//	- We create a forwarding rule with the given IP.
//		- If this ip doesn't exist in GCE, we create another one in the hope
//		  that they will rectify it later on.

[bowei]

/lgtm

[bowei]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bowei, prameshj

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

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