Grading Checklist

• Identifies that the ResourceQuota in the namespace prevents pod creation due to exceeded limits.
• Uses kubectl describe quota -n staging to see current usage vs. hard limits.
• Checks ReplicaSet events for the specific quota violation error message.
• Explains that when a ResourceQuota exists for compute resources, all containers must specify requests and limits.
• Identifies whether the issue is quota exhaustion (not enough headroom) or missing resource specs on the pod.
• Proposes solutions: increase quota, reduce requests on the new deployment, or free up quota by scaling down other workloads.
• Mentions that failed pod creation events appear on the ReplicaSet, not the Deployment.
• Notes that kubectl get pods shows nothing because pods were never created (rejected at admission).
• Recommends checking for completed Jobs or Evicted pods that still consume quota.
• Suggests implementing a LimitRange to provide default requests/limits automatically.
• Explains the relationship between ResourceQuota, LimitRange, and admission controllers.