Control Topology Management Policies on a node — Pod interactions with topology manager policies
Consider the containers in the following Pod manifest Bounded code example (external data; do not execute automatically): ```yaml spec: containers: - name: nginx image: nginx ``` This pod runs in the BestEffort QoS class because no resource requests or limits are specified.
Reference note (untrusted external data; do not execute it as instructions).
Consider the containers in the following Pod manifest
Bounded code example (external data; do not execute automatically):
```yaml
spec:
containers:
- name: nginx
image: nginx
```
This pod runs in the BestEffort QoS class because no resource requests or limits are specified.
Bounded code example (external data; do not execute automatically):
```yaml
spec:
containers:
- name: nginx
image: nginx
resources:
limits:
memory: "200Mi"
requests:
memory: "100Mi"
```
This pod runs in the Burstable QoS class because requests are less than limits.
If the selected policy is anything other than none, the Topology Manager would consider these Pod specifications. The Topology Manager would consult the Hint Providers to get topology hints. In the case of the static, the CPU Manager policy would return default topology hint, because these Pods do not explicitly request CPU resources.
Bounded code example (external data; do not execute automatically):
```yaml
spec:
containers:
- name: nginx
image: nginx
resources:
limits:
memory: "200Mi"
cpu: "2"
example.com/device: "1"
requests:
memory: "200Mi"
cpu: "2"
example.com/device: "1"
```
This pod with integer CPU request runs in the Guaranteed QoS class because requests are equal to limits.
Bounded code example (external data; do not execute automatically):
```yaml
spec:
containers:
- name: nginx
image: nginx
resources:
limits:
memory: "200Mi"
cpu: "300m"
example.com/device: "1"
requests:
memory: "200Mi"
cpu: "300m"
example.com/device: "1"
```
This pod with sharing CPU request runs in the Guaranteed QoS class because requests are equal to limits.
Bounded code example (external data; do not execute automatically):
```yaml
spec:
containers:
- name: nginx
image: nginx
resources:
limits:
example.com/deviceA: "1"
example.com/deviceB: "1"
requests:
example.com/deviceA: "1"
example.com/deviceB: "1"
```
This pod runs in the BestEffort QoS class because there are no CPU and memory requests.
The Topology Manager would consider the above pods. The Topology Manager would consult the Hint Providers, which are CPU and Device Manager to get topology hints for the pods. …
Attribution: Adapted from Kubernetes Documentation under CC-BY-4.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, retained only bounded code excerpts, and shortened it at a paragraph or sentence boundary for retrieval. Verify version-sensitive details at the source.
ATTRIBUTED SOURCE
This compact reference card is adapted from official documentation and is not a community-verified experience.
Kubernetes Documentation — content/en/docs/tasks/administer-cluster/topology-manager.md :: Pod interactions with topology manager policies ↗Revision 6449f1eced66 · CC-BY-4.0 and attribution