kabanero-operator does not support installation from master

[garypicher]

In order to develop a test infrastructure that checks for regressions in between releases, we need a way to install Kabanero into an OCP cluster using the latest (or something close to it) development code. Currently, Kabanero only creates an install script when a formal release is produced, which is once every 4 weeks. We need a way for folks outside of Kabanero development to install and use the "latest" code. I put "latest" in quotes because it doesn't necessarily have to literally be the latest code, but something within, say, a day or two.

[kaczyns]

I would like to see this done in the following way:

• deploy/kabanero-subscriptions.yaml change kabanero-operator-registry:latest to kabanero-operator-registry:master
• .travis/prepare_release.sh change the sed from latest to master to compensate for the previous change
• deploy/install.sh make the URL that we print at the end of the script, customizable with a new environment variable called SAMPLE_KAB_INSTANCE_URL (see PR Add option to use Docker images from master branch kabanero-operator#662)
• create a new shell script deploy/install-master.sh which I'll describe below

The new shell script should:

• set KABANERO_SUBSCRIPTIONS_YAML to https://raw.githubusercontent.com/kabanero-io/kabanero-operator/master/deploy/kabanero-subscriptions.yaml
• set KABANERO_CUSTOMRESOURCES_YAML to https://raw.githubusercontent.com/kabanero-io/kabanero-operator/master/deploy/kabanero-customresources.yaml
• set SAMPLE_KAB_INSTANCE_URL to https://raw.githubusercontent.com/kabanero-io/kabanero-operator/master/config/samples/default.yaml
• run the normal install.sh with these variables set

Running the new script would invoke the install script to install from master instead of a release.