k3s and containerd: system-resources flag impact on sandbox image pulling
0 reputation · 24 Jan 2025, 20:43 UTC
Resource Management for System Containers
In k3s (v1.28+), the system-resources flag allows system containers to be scheduled and managed as regular pods. This alters how the kubelet interacts with containerd regarding resource isolation and the lifecycle of pod sandboxes.
Performance Uncertainty
Under high pod density, the process of pulling sandbox images via containerd can become a significant bottleneck, impacting overall pod startup latency. There is an unresolved design decision regarding whether enabling system-resources improves this throughput by providing better scheduling flexibility or degrades node stability by introducing resource contention between system processes and user workloads.
It is unclear how the enforcement of resource limits for these system containers specifically affects the containerd image pull pipeline when this flag is toggled.
- Does enabling
system-resourceschange the priority or resource allocation for containerd's sandbox image pulling process? - What is the measurable impact of this flag on pod startup latency during high-density bursts?
k3s