Bug ID 1596037: QoS Class is showing 'Burstable' for tmm pods after enabling 'blobd'

Last Modified: Nov 29, 2025

Affected Product(s):
BIG_IP_NEXT(CNF) CNF(all modules)

Fixed In:
1.4.0

Opened: Jun 13, 2024

Severity: 3-Major

Symptoms

Kubernetes assigns the Burstable QOS class to a pod when a container in the pod has more resource limit than the request value

Impact

TMM pod QOS class is not guaranteed

Conditions

Burstable QoS Class: Kubernetes assigns the Burstable QOS class to a pod when a container in the pod has more resource limit than the request value

Workaround

In f5ingress/values.yaml for blobd container, set resource limits and ensure the requests are equal resources: limits: cpu: "1" memory: "4Gi" requests: cpu: "1" memory: "4Gi"

Fix Information

Resource Limits and Requests must be identical for all containers to get the Guaranteed Quality of Service for pods

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips