Closed L3o-pold closed 2 years ago
Make sure your Kubernetes cluster runs with Weave CNI otherwise Broadcast/Multicast/Unicast won't work.
@rennokki changing my CNI is not an option. Is there an other way? Redis adapter should work?
Also, a note about the Weave CNI on the readme/documentation could be great.
Redis is the best choice in this case.
There are still alternatives to direct pod-to-pod communication at the moment that are under development, in the future maybe one of them would work properly for CNIs that has bad or no support for Broadcast/Multicast/Unicast.
The helm chart do not seems to handle horizontal scaling. Following the https://docs.soketi.app/advanced-usage/horizontal-scaling/clustering documentation, I used the following env vars.
I ended with 3 nodes that were elected master with the following logs:
Is it normal or a configuration issue on my side or a known issue? Message are not always broadcaster to client, depending on which node is connected the client.