A team cannot create additional ConfigMaps in the finance namespace even though CPU and memory quota still show headroom. Which ResourceQuota capability most likely explains the deny?
Select an answer to reveal the explanation.
Short Explanation
Quotas are not only about CPU piles — they can also count how many ConfigMaps, Secrets, or PVCs exist. Hitting the object counter blocks creates even when compute still has room. Check the hard counts on the ResourceQuota.
Full Explanation
ResourceQuota supports both compute resource quantities and object-count limits such as configmaps, secrets, persistentvolumeclaims, and pods. Exhausting an object-count hard limit denies creation of that object type even if CPU and memory quotas remain available. Operators and developers should read all hard fields when creates fail with quota errors.