Kubernetes example is broken on updated version of Jitsi

A few things seem to be missing with the Kubernetes example, especially since the recent jitsi upgrade that turns on websockets by default (and doesn’t seem to be able to turn them off).

As it stands, if I try to run the kubernetes scripts, I end up running into the problem where the websockets are trying to connect to “wss://localhost:8443.” This is fixed by adding PUBLIC_URL to the web environment. However, even with that fix, something is still wrong with the forwarding because I’m getting errors connecting to those sockets (this seems to be the problem with #952 )

Can we either get the kubernetes example to use a compatible version of the docker containers or get it updated to actually have the right environment variables for the latest defaults from the jitsi docker containers? Thanks.

[saghul]

I’m leaning towards removing the k8s example and moving it to https://github.com/jitsi-contrib

Are there volunteers (@marner2 already volunteered and got added) that want to work on this over at jitsi-contrib?

[rsoika]

I think I figured it out. The important part is that the environment variable PUBLIC_URL is set for both - the web container and the prosody container and also it is very important, that this URL does not have a tailing / . A tailing / is no problem for the web container but if you add a tailing / to the prosody container you will see the 403 error for the resource /xmpp-websocket?room=…

So finally the environment variables for my kubernetes setup look now like this:

    - name: jvb
      env:
        - name: DOCKER_HOST_ADDRESS
          value: localhost

    - name: web
      env:
        - name: ENABLE_XMPP_WEBSOCKET
          value: "1"
        - name: PUBLIC_URL
          value: "https://meeting.foo.com"

    - name: prosody
      env:
        - name: PUBLIC_URL
          value: "https://meeting.foo.com"

And it is not necessary to expose port 9090

I will create a new pull request soon…