Add local registry for build from source workflow

[psschwei]

Currently, for doing a build from source deploy the operator will push the image to a container registry.

What if the operator created a local registry and stored built images there? In theory, this might reduce some of the push/pull traffic and speed up the build/deploy process.

It's been a long time since I've been in the weeds of Tekton, so I can't remember if the image would be available on the cluster after a Tekton build... if it is, then feel free to close this as unnecessary.

[pdettori]

Hi @psschwei - by default there is no built-in local registry in Kubernetes, nor does Tekton provide any (however, OpenShift comes with one). I agree that it would be convenient to have one, especially for a Quickstart type of setup. I did something like this before installing the docker container registry, although there was some issue there as the kubelet requires TLS certs signed by a CA and to make things simple I disabled TLS.

[cwiklik]

Hi @pdettori - is this the way?

kind create cluster --name my-kind-cluster --with-registry localhost:5000

[psschwei]

For kind, I believe this is the recommended way to create a local registry.

For remote clusters, I was thinking of something like either the OpenShift registry or a bespoke service on vanilla Kubernetes such as in this blog.

For non-Openshift clusters, there's a very good chance this may end up being more trouble than its worth...

[cwiklik]

I ended up adopting Paolo's way for local registry. Modified install.sh script to create Kind cluster and local registry.