Goal

As a developer, I want to see Kubernetes Events emitted for Triggers so that I can debug the trigger configurations when it does not behave as expected.

Debugging triggers is currently very difficult given that the errors are mostly available on the trigger controller and webhook pod logs and developers don't have access to the openshift-pipelines namespace for looking into those logs. The outcome is that users have no way to debug when they are faced with sitatuions when they create triggertemplate and eventlisteners, adds a webhook to their Git repository and see no pipelinerun is created on Git events.

Triggers should emit Kubernetes events on both success and failure scenarios within the respective user namespace to enable users to get more details about webhooks and to be able to debug when necessary.

Acceptance Criteria

• Trigger emits Kubernetes Events when a webhook is successfully processes in the user namespace
• Trigger emits Kubernetes Events when webhook processing has failed and provided sufficient details for the cause of failure

Previous Work

• Upstream work: https://github.com/tektoncd/triggers/issues/649

Notes

• A follow-up epic for improving error messages for Triggers is needed. The messages need to be more descriptive to assist the user with debugging
• There might be errors that are not possible to publish in the user namespace because user namespace cannot be determined. What can be done for those errors to improve the debugging UX?