You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to a failure of one of our Kubernetes nodes, a few NATS messages didn't trigger Argo workflows correctly. The messages are there, Argo Events just didn't pick them up correctly.
I want to make this part more reliable. Is it possible to turn the Argo event source into a durable NATS consumer? If yes, how?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Due to a failure of one of our Kubernetes nodes, a few NATS messages didn't trigger Argo workflows correctly. The messages are there, Argo Events just didn't pick them up correctly.
I want to make this part more reliable. Is it possible to turn the Argo event source into a durable NATS consumer? If yes, how?
Beta Was this translation helpful? Give feedback.
All reactions