Configure Quality of Service for Pods
Kubernetes Docs · نسخهٔ f284a9e7c87f · CC BY 4.0 برای مستندات و مجوزهای همراه
<!-- overview -->
This page shows how to configure Pods so that they will be assigned particular {{< glossary_tooltip text="Quality of Service (QoS) classes" term_id="qos-class" >}}. Kubernetes uses QoS classes to make decisions about evicting Pods when Node resources are exceeded.
When Kubernetes creates a Pod it assigns one of these QoS classes to the Pod:
- Guaranteed
- Burstable
- BestEffort
{{< note >}} Kubernetes assigns the QoS class when the Pod is created, and it remains unchanged for the lifetime of the Pod. If you attempt to resize the Pod's resources to values that would result in a different QoS class, control plane rejects your request with an error message. {{< /note >}}
{{% heading "prerequisites" %}}
{{< include "task-tutorial-prereqs.md" >}}
You also need to be able to create and delete namespaces.
<!-- steps -->
Create a namespace
Create a namespace so that the resources you create in this exercise are isolated from the rest of your cluster.
kubectl create namespace qos-exampleCreate a Pod that gets assigned a QoS class of Guaranteed
For a Pod to be given a QoS class of Guaranteed:
- Every Container in the Pod must have a memory limit and a memory request.
- For every Container in the Pod, the memory limit must equal the memory request.
- Every Container in the Pod must have a CPU limit and a CPU request.
- For every Container in the Pod, the CPU limit must equal the CPU request.
These restrictions apply to init containers and app containers equally. Ephemeral containers cannot define resources so these restrictions do not apply.
Here is a manifest for a Pod that has one Container. The Container has a memory limit and a memory request, both equal to 200 MiB. The Container has a CPU limit and a CPU request, both equal to 700 milliCPU:
{{% code_sample file="pods/qos/qos-pod.yaml" %}}
Create the Pod:
kubectl apply -f https://k8s.io/examples/pods/qos/qos-pod.yaml --namespace=qos-exampleView detailed information about the Pod:
kubectl get pod qos-demo --namespace=qos-example --output=yamlThe output shows that Kubernetes gave the Pod a QoS class of Guaranteed. The output also verifies that the Pod Container has a memory request that matches its memory limit, and it has a CPU request that matches its CPU limit.
spec:
containers:
...
resources:
limits:
cpu: 700m
memory: 200Mi
requests:
cpu: 700m
memory: 200Mi
...
status:
qosClass: Guaranteed{{< note >}} If a Container specifies its own memory limit, but does not specify a memory request, Kubernetes automatically assigns a memory request that matches the limit. Similarly, if a Container specifies its own CPU limit, but does not specify a CPU request, Kubernetes automatically assigns a CPU request that matches the limit. {{< /note >}}
<!-- 4th level heading to suppress entry in nav -->
Clean up {#clean-up-guaranteed}
Delete your Pod:
kubectl delete pod qos-demo --namespace=qos-exampleCreate a Pod that gets assigned a QoS class of Burstable
A Pod is given a QoS class of Burstable if:
- The Pod does not meet the criteria for QoS class
Guaranteed. - At least one Container in the Pod has a memory or CPU request or limit.
Here is a manifest for a Pod that has one Container. The Container has a memory limit of 200 MiB and a memory request of 100 MiB.
{{% code_sample file="pods/qos/qos-pod-2.yaml" %}}
Create the Pod:
kubectl apply -f https://k8s.io/examples/pods/qos/qos-pod-2.yaml --namespace=qos-exampleView detailed information about the Pod:
kubectl get pod qos-demo-2 --namespace=qos-example --output=yamlThe output shows that Kubernetes gave the Pod a QoS class of Burstable:
spec:
containers:
- image: nginx
imagePullPolicy: Always
name: qos-demo-2-ctr
resources:
limits:
memory: 200Mi
requests:
memory: 100Mi
...
status:
qosClass: Burstable<!-- 4th level heading to suppress entry in nav -->
Clean up {#clean-up-burstable}
Delete your Pod:
kubectl delete pod qos-demo-2 --namespace=qos-exampleCreate a Pod that gets assigned a QoS class of BestEffort
For a Pod to be given a QoS class of BestEffort, the Containers in the Pod must not have any memory or CPU limits or requests.
Here is a manifest for a Pod that has one Container. The Container has no memory or CPU limits or requests:
{{% code_sample file="pods/qos/qos-pod-3.yaml" %}}
Create the Pod:
kubectl apply -f https://k8s.io/examples/pods/qos/qos-pod-3.yaml --namespace=qos-exampleView detailed information about the Pod:
kubectl get pod qos-demo-3 --namespace=qos-example --output=yamlThe output shows that Kubernetes gave the Pod a QoS class of BestEffort:
spec:
containers:
...
resources: {}
...
status:
qosClass: BestEffort<!-- 4th level heading to suppress entry in nav -->
Clean up {#clean-up-besteffort}
Delete your Pod:
kubectl delete pod qos-demo-3 --namespace=qos-exampleCreate a Pod that has two Containers
Here is a manifest for a Pod that has two Containers. One container specifies a memory request of 200 MiB. The other Container does not specify any requests or limits.
{{% code_sample file="pods/qos/qos-pod-4.yaml" %}}
Notice that this Pod meets the criteria for QoS class Burstable. That is, it does not meet the criteria for QoS class Guaranteed, and one of its Containers has a memory request.
Create the Pod:
kubectl apply -f https://k8s.io/examples/pods/qos/qos-pod-4.yaml --namespace=qos-exampleView detailed information about the Pod:
kubectl get pod qos-demo-4 --namespace=qos-example --output=yamlThe output shows that Kubernetes gave the Pod a QoS class of Burstable:
spec:
containers:
...
name: qos-demo-4-ctr-1
resources:
requests:
memory: 200Mi
...
name: qos-demo-4-ctr-2
resources: {}
...
status:
qosClass: BurstableRetrieve the QoS class for a Pod
Rather than see all the fields, you can view just the field you need:
kubectl --namespace=qos-example get pod qos-demo-4 -o jsonpath='{ .status.qosClass}{"\n"}'BurstableClean up
Delete your namespace:
kubectl delete namespace qos-example{{% heading "whatsnext" %}}
For app developers
- Assign Memory Resources to Containers and Pods
- Assign CPU Resources to Containers and Pods
For cluster administrators
- Configure Default Memory Requests and Limits for a Namespace
- Configure Default CPU Requests and Limits for a Namespace
- Configure Minimum and Maximum Memory Constraints for a Namespace
- Configure Minimum and Maximum CPU Constraints for a Namespace
- Configure Memory and CPU Quotas for a Namespace
- Configure a Pod Quota for a Namespace
- Configure Quotas for API Objects
- Control Topology Management policies on a node