Remote Content Execution with RStudio Connect and Kubernetes
summary
Announces Off-Host Content Execution for RStudio Connect using Kubernetes: content jobs run in external pods instead of the Connect host, bundled with the Job Launcher and currently offered as a beta. Requires a Kubernetes cluster, kubectl, Helm charts, a Postgres database and ReadWriteMany shared storage (NFS/EFS). Publishers keep the same UX, can target execution images or let Connect map versions automatically; expect slightly longer cold starts from image pulls and job spawning. Installation demonstrated via Helm values.yaml and helm upgrade --install.
AI-written summary · about
chapters (6)
- 0:00Introduction to Connect
- 2:10Off-host execution launch
- 4:51User experience demo
- 8:28Administrator requirements
- 10:22Speed-run installation
- 18:11Conclusion and acknowledgments
related talks
19mRemote Content Execution with RStudio Connect and Kubernetes
19mConnect on Kubernetes: Content-level Containerization
22mRStudio Connect Past, present, and future
18mJob Launcher Changing where we run R stuff
17mSimplifying K8s Connectivity With a Powerful CLI for SRE's
12mUsing Jupyter with RStudio Server Pro
15mR Markdown + RStudio Connect + R Shiny
36mBuilding a Scalable Data Science & Machine Learning cloud using Kubernetes
