time of this writing, Knative is still a very young project and is moving fast. The sec‐ tion “Knative Build” on page 230 gives an overview of Knative and provides examples for building images in a Kubernetes cluster with the help of Knative build. Let’s have a look at OpenShift build first. Red Hat OpenShift is an enterprise distribution of Kubernetes. Besides supporting everything Kubernetes supports, it adds a few enterprise-related features like an inte‐ grated container image registry, single sign-on support, and a new user interface, and also adds a native image building capability to Kubernetes. OKD (formerly known as OpenShift Origin) is the upstream open source community edition distribution that contains all the OpenShift features. OpenShift build was the first cluster-integrated way of directly building images man‐ aged by Kubernetes. It supports multiple strategies for building images: Takes the source code of an application and creates the runnable artifact with the help of a language-specific S2I builder image and then pushes the images to the integrated registry. Use a Dockerfile plus a context directory and creates an image as a Docker dae‐ mon would do. Map a build to build jobs of an internally managed Jenkins server by allowing the user to configure a Jenkins pipeline. Give you full control over how you create your image. Within a custom build, you have to create the image on your own within the build container and push it to a registry. The input for doing the builds can come from different sources: Repository specified via a remote URL from where the source is fetched. A Dockerfile that is directly stored as part of the build configuration resource. Another container image from which files are extracted for the current build. This source type allows for  chained builds , as we see in Example 25-2. Solution  |  223 Image Dockerfile Git Custom Builds Pipeline Builds Docker Builds Source-to-Image (S2I) OpenShift Build