A seasonal licensing API should run with Burstable QoS so it can use spare capacity above its baseline. How should requests and limits be set?
Select an answer to reveal the explanation.
Short Explanation
Burstable is a soft reservation with room to stretch—request the baseline, limit the ceiling higher. When requests sit below limits, QoS lands on Burstable. Equal requests and limits is Guaranteed; nothing reserved is BestEffort.
Full Explanation
Kubernetes QoS classes derive from request/limit relationships. Burstable applies when at least one container sets a request or limit and requests are not equal to limits for all resources (commonly requests < limits). Guaranteed requires requests equal limits for CPU and memory on all containers. Omitting both yields BestEffort, not Guaranteed or Burstable by naming alone.