Introducing Tekton Triggers

In Chapter 1, A Brief History of CI/CD, you saw how continuous deployment refers to automatically deploying an application when changes are made to the code. So far, in all the Tekton examples you've seen, you had to trigger the pipeline for it to start manually. It is now time to bring the automation processes one step further and automatically start those pipelines as soon as some changes are pushed to your code repository.

To do so, you will use another tool called Tekton Triggers. Triggers enables you to accept incoming webhooks to your cluster and take appropriate action based on the content of these requests.

Using trigger templates, trigger bindings, and event listeners, three new objects in your Kubernetes cluster, you will be able to manipulate incoming HTTP requests, map the data into parameters, and then pass those values to your pipelines.

This process will trigger your pipeline, which would ultimately automatically deploy your...