In the kubernetes documentation here the conditions for a pod that is classified as Burstable
in regards to resource QOS is defined as
If requests and optionally limits are set (not equal to 0) for one or more resources across one or more containers, and they are not equal, then the pod is classified as Burstable. When limits are not specified, they default to the node capacity.
so basically stated differently:
requests
set for one or more resources (cpu/memory) across one or more containers in the pod.limits
are optional: if set, they should be not be equal to therequests
of the same resource.
But then later on the documentation gives the following as an example of Burstable
pod:
containers:
name: foo
resources:
limits:
cpu: 10m
memory: 1Gi
requests:
cpu: 10m
memory: 1Gi
name: bar
Note: Container bar
has no resources specified.
This example fulfils condition 1. However, it doesn't satisfy condition 2, since the limits and requests are set for one container but they are equal.
So why is this pod classified as a Burstable
pod?
K8s documentation containing QOS explanation and examples: https://github.com/kubernetes/community/blob/master/contributors/design-proposals/node/resource-qos.md#qos-classes