Each BigBlueButton server needs its own static IPv4 and IPv6 address and a static DNS subdomain, without having a HTTP reverse proxy in front of it. You'll want to run it in a very fast and efficient environment with guaranteed CPU and network ressources with low-latency between CPU scheduler slices and where outbound network traffic is cheap as well as plenty non-congested transit/peering near by.
Running BBB in linux containers or KVM/Qemu/... is fine, but Kubernetes based BBB currently is not a supported use case / environment, mainly because of the packet routing overhead and configuration overhead that Kubernetes brings with it, while not being able to make use of the advantages which Kubernetes usually brings along. For load balancing / distribution, you'll want to use something like Scalelite / B3Scale or similar instead.