Hi We have deployed Orchest on Linux server using Minikube `

Question

Hi We have deployed Orchest on Linux server using Minikube `minikube ip` didn t give us access to Orchest app so we used port forwarding `minikube kubectl port forward address public ip n orchest orchest webserver 5d8585bd64 8c6bh 8448 80` in order to have Orchest app available through our public ip 8448 This allowed us to reach Orchest web interface create project but failed at openning JupyterLab notebooks it tries to go back to project list page and then tries to enter JupyterLab then tries to go back to project list page and then JupyterLab and gets into this loop So I am thinking could it be that JupyterLab needs to be port forwarded as well But if that s the case newly created JupyterLab server pod would still fail What other options we have

Jacopo · Answer

Hi < ekeras> is the ingress addon enabled in minikube Do you see anything interesting when you run `kubectl describe ingress n orchest` About the ingress hostnames and such When it comes to hosting and exposing Orchest there are some caveats to keep in mind for example the fact that the application uses websockets for some features so whatever you are using to proxy needs to enable that This in the docs should be of help

ekeras · Answer

We have deployed Orchest to minikube using convienience install sh script which enables Ingress for minikube as well This is what I ve got from `minikube kubectl describe ingress n orchest` I don t see anything unusual ```Name auth server Labels Namespace orchest Address minikube ip address Ingress Class nginx Default backend lt default gt Rules Host Path Backends login auth server 80 172 17 0 10 80 Annotations minikube 0 Events lt none gt Name jupyter server 7814ce85 16ac 46960915b350 b929 4cbd Labels app=jupyter server project uuid=7814ce85 16ac 4696 a8f5 10944a43dd50 session uuid=7814ce85 16ac 46960915b350 b929 4cbd Namespace orchest Address minikube ip address Ingress Class nginx Default backend lt default gt Rules Host Path Backends jupyter server 7814ce85 16ac 46960915b350 b929 4cbd jupyter server 7814ce85 16ac 46960915b350 b929 4cbd 80 172 17 0 20 8888 Annotations 0 Events Type Reason Age From Message Normal Sync 59m x2 over 59m nginx ingress controller Scheduled for sync Name jupyter server 7de56ab2 3e57 461933539293 4e55 4d6c Labels app=jupyter server project uuid=7de56ab2 3e57 4619 be1e b2a5af94019f session uuid=7de56ab2 3e57 461933539293 4e55 4d6c Namespace orchest Address minikube ip address Ingress Class nginx Default backend lt default gt Rules Host Path Backends jupyter server 7de56ab2 3e57 461933539293 4e55 4d6c jupyter server 7de56ab2 3e57 461933539293 4e55 4d6c 80 172 17 0 18 8888 Annotations 0 Events lt none gt Name orchest api Labels Namespace orchest Address minikube ip address Ingress Class nginx Default backend lt default gt Rules Host Path Backends orchest api orchest api 80 172 17 0 8 80 Annotations minikube 0 Events lt none gt Name orchest controller Labels lt none gt Namespace orchest Address minikube ip address Ingress Class nginx Default backend lt default gt Rules Host Path Backends controller |$ orchest controller 80 172 17 0 2 80 Annotations $2 Events lt none gt Name orchest webserver Labels Namespace orchest Address minikube ip address Ingress Class nginx Default backend lt default gt Rules Host Path Backends orchest webserver 80 172 17 0 11 80 Annotations minikube login 0 Events lt none gt ```

Yannick · Answer

Some things that come to mind for me Maybe the device driver for minikube has impact on this We use the Docker driver ourselves Did you use another driver Did you set up an FQDN for Orchest <https docs orchest io en stable getting started installation html setting up an fqdn|link to docs> Given the ingress rules it indeed doesn t work to just port forward the `orchest webserver`

Rick Lamers · Answer

I d recommend setting up nginx on the host as described in the section referred to by < Jacopo>