Hello, We are having the following issue:
When we refresh our shiny app, which is running using ShinyProxy on a Kubernetes Cluster, the Pod that the app is running in gets a Status of ‘Completed’ and then when the app loads, we get 503 errors when it tries to call our landing page (i.e. our-domain.com/app_direct/our-app/). If we wait about 30 seconds the pod running the app wiill either first get a status of CrashLoopBackoff and then Running, or it will sometimes get status of Running, at which time if we again refresh the page, everything starts up without problems.
I assume that the pod is somehow getting a
SIGTERM signal, Is there some way to avoid that? What I also find confusing is that if we close the Tab, the pod doesn’t get status of Terminating until our
heartbeat-timeout, set in our ShinyProxy configs, is reached, as expected. Why would the behavior of refreshing versus closing the page be different?