https://github.com/feathersjs-ecosystem/feathers-sync

This will allow the replicas in kubernetes to be increased from 1 to N, while still pushing the service events to all connected clients properly.

Basically when replica1 has a create/updated event, that should be synchronized to the replica2, which should then pass the event onto the clients connected to replica2.

That way everybody will properly receive service events.

As a note in case I don't implement this myself. Adding a redis container to the evergreen Deployment in Kubernetes looks like the most stiraightforward approach, we just need a simple cross-container pub/sub channel