feat: added jigasi and jibri support

[amostech]

Description

I worked on your repository base, thank you very much for the great code and document. I am running your code with only one shard in my setup but I added jibri and jigasi support and I'd like to contribute my addition.

This is what I posted on your thread at the Jitsi community.
https://community.jitsi.org/t/multi-shard-auto-scalable-kubernetes-setup/64685/36?u=arthur_morales

To include these components to the jitsi namespace:

echo "===================================="
echo "Installing Jibri"
pushd jibri-deployment
kubectl delete -f . 
kubectl apply -f .
popd

echo "===================================="
echo "Installing Jigasi"
pushd jigasi-deployment
kubectl delete -f . 
kubectl apply -f .
popd

[janrenz]

Thanks for your PR! Can you add some notes what settings normally need to be adapted if users want to use one of these two new components?

[amostech]

Hi @janrenz, I haven't tested integrating directly on your "vanilla" repo. What I had to do in your code to get it to run was to strip down the certificate part from Let's Encrypt because I'm on baremetal kubernetes. I also had to remove the Big Blue Button components.

Aside from that, all you gotta do is tell Jigasi and Jibri to connect to Prosody in their respective yaml files. I understood your suggestion. I'll add some documentation as to which properties need to be changed and ping you here.

[congthang1]

So for Jibri we have to install Loopback device on host machine?
This may not possible if we using K8S on the cloud.

[amostech]

It works in the cloud as well. As long as you have an audio component in Linux. It's very simple to set it up.

[amostech]

@janrenz Here's a diagram of the architecture of my setup.

With this information the main env variables to configure and customize would be in the following files:

--- /jibri-deployment/configMap.yaml 
--- /jigasi-deployment/jigasi-deployment.yaml