EventSource High Availability¶
EventSource controller creates a k8s deployment (replica number defaults to 1)
for each EventSource object to watch the events. HA can be achieved by setting
spec.replicas to a number greater than 1.
Some types of the event sources do not allow multiple live clients with same
attributes (i.e. multiple clients with same
clientID connecting to a NATS
server), or multiple event source PODs will generate duplicated events to
downstream, so the HA strategies are different for different event sources.
Please DO NOT manually scale up the replicas, that might cause unexpected behaviors!
Active-Active strategy is applied to the following EventSource types.
- AWS SNS
- AWS SQS
- Bitbucket Server
- NetApp Storage GRID
spec.replicas is set to N (N > 1), all the N Pods serve traffic.
If following EventSource types have
spec.replicas > 1,
strategy is used, which means only one Pod serves traffic and the rest ones
stand by. One of standby Pods will be automatically elected to be active if the
old one is gone.
- Azure Events Hub
- GCP PubSub
Click here to learn more information about Argo Events DR/HA recommendations.