RStudio on Kubernetes - multi-user, multi-deployment best practise


I have an RStudio server running currently on my AWS EC2 machine using docker.
I'm planning to move to Kubernetes for scaling purposes.
What would you suggest to be the best practice for maintaining multi-user on a multi-deployment?

  • Is there a way to de-couple user management? Like using a database instead of Linux users.
  • can we hook up with any other OAuth service providers for authentication?

If I restart an RStudio docker container, I would like to maintain the users separately so that I can use them later when I bring them up, without me creating them again and again.

Please suggest the best practice to achieve RStudio deployment on Kubernetes and still maintain multi-user consistency without any issue.

Thanks, V

Hi @vignesh_bountiful,

The features you all named are supported by RStudio Server Pro. RStudio Server Pro supports a number of different authentication options, including Google OAuth, LDAP/AD, and proxied auth. We also recently added the launcher feature, which allows you to connect your RStudio Server Pro instance to a Kubernetes cluster and launch sessions there.

If you're interested, there's a lot more information on RStudio Server Pro, including a free 45-day trial, and the ability to schedule a demo with sales here.

You can also check out the admin guide for details on available auth mechanisms.

Hi @alexkgold,

Thanks for responding soon. We are currently using RStudio Community Edition.
Is any of the options possible in RStudio open source (free) version ?

Cheers, V

Hi @vignesh_bountiful,
I have tried Auth0 on an application presented at rstudio-conf-2018.

It works pretty well and here is the URL to the application
I wanted to test Auth0 especially for Federation.

Hope this helps