From the course: Automating Kubernetes with GitOps

Unlock this course with a free trial

Join today to access over 24,700 courses taught by industry experts.

Running Tekton triggers

Running Tekton triggers

- Okay, to make the procedure completely automated, we need one more element. We need it to be triggered automatically. That's where the trigger comes in. So the trigger is an API resource that runs a pipeline based on an external event. And it consists of three additional API resources; the EventListener, which runs a Pod that listens for specific events, the TriggerTemplate, which configures a PipelineRun when the event occurs, and the TriggerBinding, which passes the data created by the TriggerTemplate to the PipelineRun. And because the EventListener manages API objects, a ServiceAccount and RBAC configuration are required to use it. That's something that we have seen a lot. In GitOps you want the GitOps operator to do stuff in Kubernetes. You need role-based access control and a service account. You should be pretty used to that at this point. So let's check out these triggers. In the first step, we need to make sure that they are installed. So here we have the triggers latest…

Contents