Hi guys, im trying to test OCTO functionnality with latest docker images and websockets enabled. The goal is to be able to have multiple kubernetes cluster with a single shard.
1/ There is no sticky sessions mechanism yet.
2/ Only ports LB TCP/80/443 + UDP JVB 30000-3000x for stream + octo are opened to the web.
3/ Unlike https://meet.jit.si we are not exposing JVB TCP/443 on the internet
4/ Since i dont need geo mechanism, current config.js web is not configured to provide informations in deploymentInfo. (should i?)
5/ To test OCTO_BRIDGE_SELECTION_STRATEGY is set to SplitBridgeSelectionStrategy
6/ Each shard is on a different kubernetes cluster in a different AZ or region
7/ Currently, we have a single domain for each JVB and websockets and for every shard
Current architecture is :
My goal is to run OCTO configuration to be able to test a big conference using OCTO with users splitted on different shard but same region region1 (no geo needed)
The current behavior is that some participants are in the same room, and some are in others rooms.
Sometimes participants in the same room lost connectivity after time (due to websocket ?)
Could you help me to understand what i miss, i thought we could have chance using OCTO to ensure connectivity between shards but it seems i need to add some stickyness somewhere finally ? at cloud lb ? ingress ? haproxy ? elsewhere ?
Thank you for your answers