Design Container Resource Isolation · System Design Interview

Design Container Resource IsolationDesign how many containers from different teams share one host without seeing each other, starving each other, or taking the host down.What it has to do

A container sees only its own processes, filesystem and network

Each container’s CPU, memory and disk I/O are capped and, where promised, guaranteed

A container that exceeds its memory is stopped, and no other container is affected

A container has only the privileges it was granted

Scale

Containers per host: 300

Teams sharing a host: 40

Out of scope

Scheduling containers onto hosts

Image scanning

Network policy

Virtual machine based isolation

Practise this challengeAll system design challenges

LetsDiscuss

Loading your session…