Nonsensical values in Kubernetes "requests" and "limits"
Issue
- Why can values like "GigaCores" and "MilliBytes" be set in "requests" and "limits"?
- Setting "4G" as "cpu" value, which would result to "4 GigaCores"
- Setting "200m" as "memory" value, which would result to "200 MilliBytes"
- What happens if users set nonsensical values in "requests" and "limits"?
Environment
- Red Hat OpenShift Container Platform (RHOCP) 4.y
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
