1. Proposed title of this feature request

Option for ImageStream Reference Policy in oc new-app

2. What is the nature and description of the request?

As a developer deploying applications on OpenShift from an insecure registry
I would like to be able to configure `oc new-app`'s reference policy for the generated imagestream tag
So that I can have the internal registry act as a pull through cache for my insecure registry.

3. Why does the customer need this? (List the business requirements here)

oc new-app has an `--insecure-registry` option, which allows a template to be deployed using an image from an insecure registry. As a part of this process, oc new-app creates an imagestream (and tag) for the referenced image, using the "Source" reference policy. This means that the imagestreamtag acts as a shorthand/alias for the image. There is a second option - "Local" - which instructs the internal registry to act as as a proxy (aka a "pull-through cache").

The challenge is that unless the cluster is configured to pull images from the insecure registry, the deployment of the template will likely fail. Adding a new option to `oc new-app` that allows the reference policy to be set may help.

See RFE in https://bugzilla.redhat.com/show_bug.cgi?id=2046163

4. List any affected packages or components.

oc new-app (new-build)
OpenShift Templates
OpenShift Builds