Vijay Kumar

Any Update on the following issue. We are experiencing similar issue with MSK and Argo events. Eventsource Pod Logs: {"level":"info","ts":1646827808.553952,"logger":"argo-events.eventsource","caller":"cmd/main.go:63","msg":"starting eventsource server","eventSourceName":"kafka","version":"vv1.3.1+f47cb23.dirty"} {"level":"info","ts":1646827808.55421,"logger":"argo-events.eventsource","caller":"metrics/metrics.go:172","msg":"starting metrics server","eventSourceName":"kafka"} {"level":"info","ts":1646827808.5563707,"logger":"argo-events.eventsource","caller":"leaderelection/leaderelection.go:122","msg":"Not the LEADER, stand by...

Ive been facing the same issue and have a workaround for the same which goes like this: 1. AWS have instance Lifecycle for all insatnces which starts with "Warmed" for...