trame in kubernetes + wslink

[JT3DAI]

So I can deploy a trame paraview app to Kubernetes in GCP and it works fine when I overwrite the wslink functionality by overriding the main entrypoint for the trame docker image, using a custom command in my deployment.

Now I would like to give each user there own session per browser tab in GCP. This works great in docker compose locally but when I push to using Kubernetes I cannot get a browser to connect using wslink and the browser times out.

Session did not start before timeout expired. Check session logs.

So before I got too far

1. Should I be able to configure Kubernetes to work with wslink and the trame docker image?
2. If so, are there any examples on what I should have in my deployment,, service and ingress yml files. In particular what ports should I be exposing. I presume it is just port 80?

For example in service I have this

spec:
  type: ClusterIP
  selector:
    app: mi-ui
  ports:
    - name: http
      port: 80
      targetPort: 80

and the ingress I have

            backend:
              service:
                name: mi-ui
                port:
                  number: 80

and in deploy i have this

          ports:
            - containerPort: 80

Thanks

[bourdaisj]

Yes you can make trame / wslink work with Kubernetes.

Session did not start before timeout expired. Check session logs.

Did you check the logs? Usually it contains information that will help you troubleshoot why the session did not start.
To me, if you get this error message in the browser that means your kubernetes/network configuration is correct.
By default the logs are located here in the container: /deploy/server/logs

[JT3DAI]

ahh I was looking or the complicated answer and you were right. Logs show I was getting this error

OSError: [Errno 99] error while attempting to bind on address ('::1', 9500, 0, 0): cannot assign requested address

I should be binding to 0.0.0.0. Correct?