[Solved] Identify the reason why this pod is classified as Burstable instead of Guaranteed:resources: requests: cpu: '300m' memory: '256Mi' limits: cpu: '300m' memory: '256Mi' extra: 'value' | Kubernetes

Kubernetes - Resource Management

Identify the reason why this pod is classified as Burstable instead of Guaranteed:

resources:
  requests:
    cpu: '300m'
    memory: '256Mi'
  limits:
    cpu: '300m'
    memory: '256Mi'
  extra: 'value'

ACPU limits are less than requests

BRequests and limits are equal, so it should be Guaranteed

CMemory requests are missing

DThe presence of an unsupported 'extra' field in resources

Step-by-Step Solution

Solution:

Step 1: Check resource requests and limits
CPU and memory requests and limits are equal, which normally qualifies for Guaranteed.
Step 2: Identify invalid fields
The 'extra' field is not valid under resources and causes the pod spec to be invalid or ignored for QoS classification.
Step 3: Effect on QoS classification
Due to the invalid field, Kubernetes falls back to Burstable QoS.
Final Answer:
The presence of an unsupported 'extra' field in resources -> Option D
Quick Check:
Invalid resource fields cause fallback to Burstable [OK]

Quick Trick: Invalid resource fields cause Burstable, not Guaranteed [OK]

Common Mistakes:

Master "Resource Management" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

More Kubernetes Quizzes

Identify the reason why this pod is classified as Burstable instead of Guaranteed: