Connect on Kubernetes: Content-level Containerization
summary
Connect decouples publishing from runtime by running applications as containers on Kubernetes: Connect spawns pods via a launcher service that talks to the Kubernetes API and enforces CPU and memory limits. The UI shows per-deployment execution environment images and service-account options for fine-grained data access. Environment reconstruction normally uses the NFS persistent volume and a runtime cache, but reconstruction can be bypassed when baked images contain dependencies, improving cold-start latency under the off-host execution model.
AI-written summary · about
chapters (6)
- 0:00Connect on Kubernetes intro
- 3:14What Connect does
- 5:39Off-host execution in K8s
- 8:07Fine-grained resource control
- 12:24Q&A on Slurm clusters
- 15:16Building custom images
related talks
19mRemote Content Execution with RStudio Connect and Kubernetes- 19mRemote Content Execution with RStudio Connect and Kubernetes
32mLocal development techniques with Kubernetes
39mMore Than Secure: Containerd + KataContainers as Kubernetes Runtime
01h 01mDeploying Kubernetes, a Container Cluster Manager
01h 17mIntro + Deep Dive: containerd
30mClosing the Developer Experience Gap of your Container Platforms
37mManaging Containers at Scale with CoreOS and Kubernetes