dockerfile : |- FROM openjdk:8-alpine COPY *.jar / CMD java -jar /*.jar strategy : type : Docker output : to : kind : ImageStreamTag name : random-generator:latest triggers : -  imageChange : automatic : true from : kind : ImageStreamTag name : random-generator-build:latest type : ImageChange Image source references the ImageStream that contains the result of the S2I build run and selects a directory within the image that contains the compiled JAR archive. Dockerfile source for the Docker build that copies the JAR archive from the ImageStream generated by the S2I build. The  strategy  selects a Docker build. Rebuild automatically when the S2I result ImageStream changes—after a success‐ ful S2I run to compile the JAR archive. Register listener for image updates and do a redeploy when a new image has been added to the ImageStream. You can find the full example with installation instructions in our example repository. As mentioned, OpenShift build, along with its most prominent S2I mode, is one of the oldest and most mature ways to safely build container images within a Kubernetes cluster with OpenShift flavor. Let’s look at another way to build container images within a vanilla Kubernetes cluster. Solution  |  229