jitsi-kubernetes | Jitsi deployment on Kubernetes with JVB autoscale | Continuous Deployment library

by congthang1 Shell Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | jitsi-kubernetes Summary

jitsi-kubernetes is a Shell library typically used in Devops, Continuous Deployment, Nginx, Docker applications. jitsi-kubernetes has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Kubernete deployment with autoscale JVB and OCTO enabled Kubernetes 1.18.10. There are 4 parts of this deploy, each will be on a kuberenetes. Meaning you need 4 kubernetes for 2 regions or 2 kubernetes for only 1 region. The autoscale will not work if you put jvb on the same Web Prosody kubernetes. JVB nodes need at least 2 cpu. Make sure you have save your context connection to your kubernetes cluster on cloud. Your scaleable jitsi with octo will be avaiable at the main domain! On digitalocean point your domain to the load balancer created on kuberenets main web and second region one. You need to set certificate there too for port 443 on setting of load balancer. If you have more region just redo from step 3.

Support

Quality

Security

License

Reuse

Support

jitsi-kubernetes has a low active ecosystem.

It has 15 star(s) with 14 fork(s). There are 3 watchers for this library.

It had no major release in the last 6 months.

There are 2 open issues and 4 have been closed. On average issues are closed in 88 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of jitsi-kubernetes is current.

Quality

jitsi-kubernetes has 0 bugs and 0 code smells.

Security

jitsi-kubernetes has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

jitsi-kubernetes code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

jitsi-kubernetes is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

jitsi-kubernetes releases are not available. You will need to build from source code and install.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of jitsi-kubernetes

Get all kandi verified functions for this library.

jitsi-kubernetes Key Features

No Key Features are available at this moment for jitsi-kubernetes.

jitsi-kubernetes Examples and Code Snippets

No Code Snippets are available at this moment for jitsi-kubernetes.

Community Discussions

Trending Discussions on jitsi-kubernetes

How to setup Jitsi Meet on a custom Kubernetes

QUESTION

How to setup Jitsi Meet on a custom Kubernetes

Asked 2022-Mar-25 at 04:50

We have a single node kubernetes environment hosted on an on prem server and we are attempting to host jitsi on it as a single pod. Jitsi web, jicofo, jvb and the prosody will be in on one pod rather than having separate pods for each (reference here)

So far what we have managed to set it up by adding our ingress hostname to as the PUBLIC_URL to all 4 containers within the pod. This service works fine if two users are on the same network.

If a user using another network joins the call, there is no video or audio and will receive such an error in the jvb container

JVB 2022-03-16 02:03:28.447 WARNING: [62] [confId=200d989e4b048ad3 gid=116159 stats_id=Durward-H4W conf_name=externalcropsjustifynonetheless@muc.meet.jitsi ufrag=4vfdk1fu8vfgn1 epId=eaff1488 local_ufrag=4vfdk1fu8vfgn1] ConnectivityCheckClient.startCheckForPair#374: Failed to send BINDING-REQUEST(0x1)[attrib.count=6 len=92 tranID=0xBFC4F7917F010AF9DA6E21D7] java.lang.IllegalArgumentException: No socket found for 172.17.0.40:10000/udp->192.168.1.23:42292/udp at org.ice4j.stack.NetAccessManager.sendMessage(NetAccessManager.java:631) at org.ice4j.stack.NetAccessManager.sendMessage(NetAccessManager.java:581) at org.ice4j.stack.StunClientTransaction.sendRequest0(StunClientTransaction.java:267) at org.ice4j.stack.StunClientTransaction.sendRequest(StunClientTransaction.java:245) at org.ice4j.stack.StunStack.sendRequest(StunStack.java:680) at org.ice4j.ice.ConnectivityCheckClient.startCheckForPair(ConnectivityCheckClient.java:335) at org.ice4j.ice.ConnectivityCheckClient.startCheckForPair(ConnectivityCheckClient.java:231) at org.ice4j.ice.ConnectivityCheckClient$PaceMaker.run(ConnectivityCheckClient.java:938) at org.ice4j.util.PeriodicRunnable.executeRun(PeriodicRunnable.java:206) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829)

Furthermore the errors in the browser console are as such

EDIT

I have added the yaml file for the jitsi here

...

ANSWER

Answered 2022-Mar-25 at 04:50

Managed to fix it. Posting this for anyone who comes across the same issue.

first off the UDP port 10000 does not work in kubernetes as you can only expose ports between 30000 to 32768. Having said that you need to pick a port within that range and use it for the JVB_PORT configuration in the JVB container.

secondly use that port in the service lay to expose it to the front end

Source https://stackoverflow.com/questions/71495351

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install jitsi-kubernetes

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: