WIP: Allow setting router image in hack/release-local.sh

[rfredette]

The default router image in the ingress operator deployment manifest is not up to date, and sometimes causes red herring issues when debugging changes.

With this change, a user can set the IMAGE environment variable to a router image pullspec, and hack/release-local.sh will update the deployment manifest to use the specified image.

Alternatively, a user can set the GET_IMAGE environment variable to a non-empty value, and hack/release-local.sh will query the cluster in the user's default kubeconfig to automatically get the router image currently in use and use the same image in its generated manifests. Note that GET_IMAGE requires read access to the openshift-ingress-operator/ingress-operator deployment.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from rfredette. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• 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]

@rfredette: 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/e2e-gcp-operator	ebf53e5	link	true	/test e2e-gcp-operator

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.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale