Class Resources: Kubernetes’ Fastest Way Of Shushing Noisy Neighbors

The conference presentation discusses resource management in Kubernetes and the implementation of Quality of Service (QoS) classes to prioritize resource allocation for pods.

• Kubernetes is implementing QoS classes to prioritize resource allocation for pods
• The responsibility of balancing resources falls on the admin
• There is no automatic reconciliation for resource allocation when pods disappear
• Future work includes making explicit the Pod QoS class and implementing new types of resources

The speaker explains that the admin is responsible for balancing resources and ensuring there are enough classes for the pods. The container runtime does not have a view of the node and cannot automatically reconcile resource allocation when pods disappear. This highlights the importance of proper resource management and allocation in Kubernetes to avoid resource contention and ensure optimal performance.

Is your application disturbed by noisy neighbors, abusing communal resources that are out of your control? Currently in Kubernetes, there are some resources that workloads are forced to share, such as cache, memory bandwidth and disk I/O. Luckily, there’s an effort to fix this with Class Resources, enabling QoS control of workloads by putting them into different classes and allowing independent control of cache allocation and memory and I/O bandwidth. In this talk, join Markus Lehtonen and Peter Hunt as they present the concept of class resources, the prior work done in the container runtimes, as well as the future of first-class integration. We invite anyone interested in managing their workload QoS to join us, be it cache allocation, memory, or disk I/O bandwidth, or interest in developing support for new types of class resources. People who join will learn that Class Resources is the best way to let your applications run in peace.