Closed J0YAL closed 6 months ago
Hi
This is quite an old issue and the mentioned problems should be fixed in the recent releases of ShinyProxy. Therefore I'm going to close this issue, but feel free to open a new issue if you still have any problem with a recent version of ShinyProxy.
I added RStudio (container-cpu-limit: 0.8 & container-memory-limit: 1Gi) to this example and deployed it to a Google Cloud Platform Kubernetes cluster with autoscaling enabled.
I was able to start RStudio with the initially allocated resources (i.e., 1.93 CPU & 5.92 GB MEM in node 1). But when I logged in as another user and tried to start RStudio, the cluster detected a resource shortage and allocated another node (i.e., node 2 with the same resources), which contained the pod that ran the 2nd RStudio instance. However, the RStudio failed to launch and returned 404 in the end. It appeared that the Proxy object involved in this process failed to get initialised for some reason.
Screenshots: screenshots.docx
Example to reproducible the error: please refer to
start.sh
for deployment 03.zipshinyproxy.log: shinyproxy.log
Thanks in advance to anyone looking into this.