Closed DancingPanda666 closed 5 months ago
This is due to WebRTC not yet supporting clustering, therefore it cannot support multiple pods. This is a known issue, and you can follow the progress of this issue at: https://github.com/ossrs/srs/discussions/3634
Duplicated to #3634
TRANS_BY_GPT4
Describe the bug Actually, I'm not sure it's a bug or it's caused by wrong srs configuration.
I deployed SRS5 in K8s enviroment. and set replicas as 2. both of 2 SRS pods are sharing same FQDN (ingress) WebRTC: test-k8s-srs-api.dev.net API: test-k8s-srs-webrtc.dev.net
then when playing WebRTC. it's possible that 2 requests doesn't send into the same pod and leads to such error "(RTC TCP packet is invalid for session not found) : process rtc tcp pkt : no session"
I was wondering if there's any way which can resolve WebRTC running on more than 2 pods (k8s env.)
Version SRS5
To Reproduce Steps to reproduce the behavior:
Expected behavior in K8s, when replicas > 1, still can always play WebRTC successfully
Screenshots
Additional context