EventListener parameters
JuMasta opened this issue · 5 comments
Discussed in #1803
Originally posted by JuMasta October 24, 2023
Hi!
We use Tekton-operator v0.68.0 version. Can I set parameters kube-api-burst and kube-api-qps to EventListener via TektonConfig or any other way. When EventListener gets 2 webhooks at the same time it gets error - "error getting secret: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline".
@JuMasta do you want to control tekton-events-controller things? Could you please elaborate the deployments details that you want to manage?
I want to manage by EventListener deployment. My log: {"severity":"info","timestamp":"2023-11-23T14:43:28.205Z","logger":"eventlistener","caller":"sink/sink.go:420","message":"interceptor stopped trigger processing: rpc error: code = FailedPrecondition desc = error getting secret: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline","commit":"","eventlistener":"github-listener-interceptor","namespace":"tekton-pipelines","/triggers-eventid":"0569848a-8c88-4c13-91c0-bea091ae72dc","eventlistenerUID":"0766dc4d-6653-4b69-83d1-32046cec7292","/triggers-eventid":"0569848a-8c88-4c13-91c0-bea091ae72dc","/trigger":""}
@JuMasta sorry for the late response, Does operator manages EventListener? I guess trigger is managed by operator and EventListener is managed by triggers controller. Am I correct?
AFAIK, we can control triggers controller kube-api-burst and kube-api-qps via options https://tekton.dev/docs/operator/tektonconfig/#additional-fields-as-options
You are correct. I can set these parameters via options to triggers-controller, but I can't find a way to set these parameters to EventListener
Thanks @JuMasta !
@savitaashture Is it possible to control the EventListeners deployment parameters with triggers-controller's deployment parameters or with a configMap?