<p>In most resource managers, we can set the container's CPU usage and memory usage.
But I'm curious about the technical reasons for not supporting disk I/O resource allocation for containers.</p>

김민우
<p>According to <a href="https://andrestc.com/post/cgroups-io/" rel="nofollow noreferrer">Using cgroups to limit I/O</a> this requires <strong>cgroups v2</strong> and that is quite recent feature for container runtimes.</p>
<p>For Kubernetes support, you should probably follow <a href="https://github.com/kubernetes/enhancements/pull/1907" rel="nofollow noreferrer">initial kep for qos of storage v0.1</a> and <a href="https://github.com/kubernetes/enhancements/issues/2254" rel="nofollow noreferrer">cgroups v2 was added as alpha feature in Kubernetes 1.22</a>.</p>
<p>So it looks like there is work in progress on this.</p>
