Now that you have the necessary YAML files to create your trigger, you will need a few more configurations to ensure that your cluster is listening. First, you will need to create a secret to be used to validate that the incoming requests. Then, you will need to expose a route so it can be reached from outside of the cluster. You will need the help of ngrok here to make sure that it is also available from the public internet, which you installed in Chapter 10, Getting Started with Triggers. Finally, you will need to add a webhook to a GitHub repository. This webhook will connect to your newly created trigger.

Creating a secret

To ensure that your pipeline is not launched every time a robot accidentally hits your trigger URL, you will need to create a secret. You could use any arbitrary string as a key, but it is a good practice to use a random key for each one of your triggers. For this reason, we will be using a random number converted...