Reducing the pods related to EventListener

[khrm]

Expected Behavior

There should be fewer pods or deployments related to EventListener.

Actual Behavior

At present, you can any number of pods handling EventListener logic. This led to wastage of resources due to the proliferations of these pods.

Additional Info

Current Proposal:
https://docs.google.com/document/d/1is5sJMkqWMnOa4fP87H39auTnWR1IKFu7TxTkMNJV5c/edit#

[vdemeester]

/kind feature

[khrm]

Summary of Discussion on this &
#456

1. Design recommended in both scenarios are based on having URL to determine EL or TriggerCRD .
2. Main issue with these designs are RBAC. Should be give RBAC permissions similar to controller for a global EventListener?
3. If we don't want to 2, then we would need to give permission to create Pod with a particular SA in every namespace to EL deployment which relates to Triggers. Now this creates another security issue that a lot of transient pods could be created by just hitting the URL.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dibyom]

Similar to #456 -> part of TEP-009 and TEP-008. I think we can keep this closed and open other issues for those two.