Controller should create EventListener pod on creation about triggers HOT 5 CLOSED

Ok, thanks Ian. I'm not extremely knowledgable about those situations where we might want a StatefulSet over a Deployment, but it seems like a Deployment will work well for us right now. Down the line, if we want to change it to a StatefulSet, we can.

from triggers.

From my understanding and according to the docs:

If an application doesn’t require any stable identifiers or ordered deployment, deletion, or scaling, you should deploy your application with a controller that provides a set of stateless replicas. Controllers such as Deployment or ReplicaSet may be better suited to your stateless needs.
Limitations

I think Deployment makes the most sense since there isn't really anything stateful to the listener pods?

from triggers.

@iancoffey do you have an opinion? Was there an advantage to using a StatefulSet for the TektonListener?

from triggers.

iirc, the reasons I chose statefulset are the Ordered, graceful deployment and scaling and Ordered, automated rolling updates properties meant it less likely two listeners of different versions be exposed at once. That seemed like a big potential problem at the time.

https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#using-statefulsets

I dont have a strong opinion and more or less just rolled with it. The set approach always worked fine but not moreso than a Deployment, in the case that we dont care about the deployment orderings (or I just misunderstand them)

from triggers.

Sorry, I should have closed this earlier from #43

from triggers.