Problem:

Downstream S2I and Buildah tasks main target group is OpenShift customers but they are not well integrated with OpenShift features like the internal registry and image streams

Goal:

As a developer, I want the downstream S2I and Buildah tasks to simply work with imagestreams out of the box so that I don’t have to reconfigure them when using them on OpenShift. S2I tasks should support specifying an imagestreams name as a param to be used as the output image for the S2I build.

Acceptance criteria:

• S2I and Buildah tasks can push to an imagestream by specifying the name of an imagestream as params
• S2I and Buildah tasks can push to any registry by specifying the full url of the target image in the destination registry

Previous work

• https://github.com/openshift/pipelines-catalog/pull/27

Customers

• Infineon