We are currently working on hosting Jitsi on Kubernetes.
However, we are now having questions regarding the autoscaling of the JVBs, each of them in an own pod:
When the autoscaler decides to scale down, we might see the case, that there is still a conference running in a pod, which is chosen to be stopped. As far as we understood, this is were the graceful_shutdown script comes into play. With the graceful_shutdown script, the JVB tells Jicofo to not allocate conferences at this JVB anymore and if the conference has ended, it ends the JVB process. Is that correct? And how does the communication with Jicofo work in detail?
Can Jicofo reallocate the conferences of exiting JVBs? This is indicated here: Scale Videobridge inside kubernetes in the answer of Kroev. If so, the conference is interrupted?
How do you deal with scaling down of JVBs at meet.jit.si? Do you run the graceful_shutdown script and wait for the conferences on a JVB to disappear? If that is the case: is your scaling mechanism blocked if there is a JVB that should be dropped, but has still conferences? What happens if another JVB does not have any conferences in the mean time? Does the scaler recognize it and shuts down this one instead? And what happens if the conference takes so long, that the system should upscale again?