This seems like a very interesting topic since I’m working on deploying ShinyProxy on a cluster environment as well. However, I feel like ShinyProxy needs to directly access docker daemon while Kubernetes abstracts away from the containers. This seems to be a conflict. And also, we need Kubernetes to spin up a pod(an instance of our Shiny application, this is the default behavior of ShinyProxy for the purpose of being able to accommodate multiple users at the same time) every time a user visits. But I’ve never used Kubernetes before, I might be completely wrong about this.
If you guys find a solution, please post here. Thanks