Chrome Cluster on K8s: Memory Config, /dev/shm, and Graceful Shutdown
Browsers aren't stateless microservices. 200-500MB per instance, /dev/shm config, WebSocket long connections — running browser clusters on K8s needs a completely different design.
Engineering Blog
Tag: browser cluster
2 posts under this tag.
Chrome Headless at Scale (Part 3): Why K8s HPA Doesn't Work for Browser Clusters
CPU-based HPA is nearly useless for browser instances. Startup CPU spikes don't mean it's serving. Memory doesn't release after close(). Browsers aren't stateless services.