 Hello, my name is Brian Tannis, and I'm with the Red Hat Club Platforms Business Unit. In this video, we're going to be focusing on an application from Coderland, the Compile Driver. The Compile Driver is a photo booth application within Coderland that is used to overlay an image, text, and the date on user's photo. It is designed with performance and efficiency in mind as it utilizes the serverless architecture to perform the heavy lifting of processing the overlay within the photo. To begin, we need to first add a project within our OpenShift cluster. After the project's been created, we need to add a few privileged security context constraints to the default service account. Our particular deployment relies on a Jenkins pipeline, so we'll go ahead and quickly roll out Jenkins ephemeral within our project. Next, we'll roll out the back-end Knative serving service. As you can see, the service definition to deploy our serverless component is very simple. We're simply telling Knative to use a pre-built container image for our image overlay. This microservice will handle the processing of the overlay within the user's photo and is the back-end component within our diagram. To run rollout, Knative will deploy a few objects within our project. You could see a deployment that has been created which is visible within the OpenShift console. A few of the other components Knative serving deploys in the cluster would be routes, configuration, and revisions. The route allows us to access our application externally. The configuration maintains a desired state for the deployment, and the revision resource is a point-in-time snapshot for the code and configuration for each modification made to that workload. The next step to deploy our Compile Driver app is to deploy our template. The template will deploy a few objects within OpenShift that are needed to run the pipeline and deploy the application. Next we need to grab our Istio Ingress Gateway service location. Knative serving utilizes an Istio Ingress Gateway to handle traffic coming into our serverless service. We will copy the location to use in our pipeline. We are going to utilize a Jenkins Pipeline to automate the deployment of the Compile Driver app on OpenShift. Our Jenkins Pipeline utilizes four stages. These stages are building and deploying the front-end and proxy microservice for the Compile Driver application. This pipeline automates setting a few environment variables that are required for both of the services to function properly. We are using the OpenShift plugin for Jenkins to allow this to happen. We will create the build configuration with the Jenkins Pipeline and start the build. Jenkins will begin running our pipeline, which will build and deploy the application. We could see the build in progress within OpenShift as well as Jenkins. When the build is done, Jenkins reports success. We'll open the Compile Driver application by heading to the route for the front-end microservice. Once the app loads, we'll take our picture. The picture will flow through the proxy service, hitting the Knative serving back-end service. The back-end service will add the overlay and respond through the proxy to the user and we'll see the photo with the overlay. When we take our photo, we could see what happens with Knative serving using the event list within OpenShift. We could see our replica set scaling up and containers being created. Once the heavy lifting of the image overlay has been processed, no more traffic comes into the service and Knative scales down the service to zero, waiting for traffic to come back. Thank you for watching. Please be on the lookout for future videos on functionality with OpenShift 4.