`$MY_NAMESPACE` should be replaced by the namespace you want to use for Jitsi Meet.
It assumes that you have a [Nginx Ingress](https://docs.nginx.com/nginx-ingress-controller/overview/) controller and you use [CertManager](https://cert-manager.io/docs/installation/kubernetes/) along with [ACME](https://cert-manager.io/docs/configuration/acme/) issuer type for managing the HTTPS certificates.
Because `--wait` flag, the status will be given once Jisti Meet is ready.
## Updating the chart
To update the chart, in your terminal, go to the `jitsi-meet-helm` repository and run the following command:
`$MY_NAMESPACE` should be replaced by the namespace you want to use for Jitsi Meet.
## Delete the chart
To delete the chart, in your terminal, go to the `jitsi-meet-helm` repository and run the following command:
```bash
helm delete --purge jitsi-meet
```
## Demo
Currently, the `aws` example is running on [`jitsi.project-meat.tk`](https://jitsi.project-meat.tk). Feel free to give it a try and share your feedback !
## Warnings
* This chart is still an experiment - it runs currently one replica of each component
* Work needs to be done for writing route tables for the ingress to route UDP / TCP
* JVB service uses a `NodePort` type for routing UDP outside of the cluster
* The chart was tested on AWS and local Kubernetes cluster **ONLY** (no ingress - `kubectl port-forward` + `ngrok` to the rescue)
* The `prosody` deployment deploys both `jicofo` and `prosody` in one pod in order to use `jicofo` as a sidecar container - maybe not wise
## Configuration
The following table lists the configurable parameters of the Jitsi Meet chart and their default values.