Search⌘ K

Examining QoS in Action

Explore how Kubernetes assigns Quality of Service (QoS) to pods by examining resource requests and limits. Understand the differences between Guaranteed, Burstable, and BestEffort QoS classes through practical examples. Learn to verify and manage these classifications to optimize resource allocation and ensure cluster stability.

Checking QoS with initial definition

Let's look at the QoS to which our `go-demo-2-db` Pod is assigned:

Shell
kubectl describe pod go-demo-2-db

The output, limited to the relevant parts, is as follows.

Shell
...
Containers:
db:
...
Limits:
cpu: 100m
memory: 100Mi
Requests:
cpu: 10m
memory: 50Mi
...
QoS Class: Burstable
...

The Pod is assigned Burstable QoS.

Note: Its limits are different from requests, so it did not qualify for Guaranteed QoS.

Since its resources are set, and it is not eligible for ...