With a solid grasp on what components make up Knative, it’s time to start looking at some more advanced topics. Serving offers quite a bit of flexibility in how to route traffic and there are other Build Templates that make building applications easy. It’s even easy to make our own Event Source with just a few lines of code. In this chapter we’ll take a deeper look at these features to see how we can make running our code on Knative even easier.
The concept of a Knative Service was introduced in Chapter 2. Recall that a Service in Knative is the combination of a single configuration plus a collection of Routes. Under the Knative and Kubernetes covers it is ultimately 0 or more containers within a Pod along with the components to make your application addressable. All of this is supported by a routing layer with robust options for traffic policies.
Whether you think of your workload as an application, container, or process, it runs as a Service in Knative. This offers flexibility to handle many scenarios, depending on which assets make up the software. This section provides another alternative that Knative provides you to build and deploy your software.
You saw in Chapter 3 that the Kaniko Build Template lets you build container images using a Dockerfile. This method tasks you with the responsibility of writing and maintaining that Dockerfile. If you prefer to remove ...