Container Resource Management Cheat Sheet

Updated 2026-03-17

Next Topic: Container Storage and Persistent Volumes Cheat Sheet

Container resource management is the practice of defining, allocating, and controlling compute resources (CPU, memory, storage) for containers running in orchestration platforms like Kubernetes and standalone runtimes like Docker. Proper resource management prevents noisy neighbor issues, ensures predictable performance through scheduling guarantees, and maximizes cluster utilization while avoiding out-of-memory kills or CPU throttling. At its core, resource management relies on two key primitives: requests (guaranteed allocations for scheduling decisions) and limits (hard caps enforced at runtime)—misaligning these causes either wasted resources or application instability. A critical mental model: Kubernetes schedules based on requests but enforces limits, meaning overcommit is common and understanding QoS classes (Guaranteed, Burstable, BestEffort) determines which pods survive resource pressure. For production workloads, always set requests equal to observed P50 usage and limits at P95 with headroom, monitor actual consumption continuously, and use autoscaling mechanisms (HPA, VPA, Cluster Autoscaler) to dynamically adapt to demand while maintaining cost efficiency.

What This Cheat Sheet Covers

This topic spans 28 focused tables and 172 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.

Table 1: Resource Units and SpecificationsTable 2: Container CPU Requests and LimitsTable 3: Container Memory Requests and LimitsTable 4: Memory Metrics and AccountingTable 5: CPU Throttling and CFS QuotaTable 6: Kubernetes QoS ClassesTable 7: Resource Quotas and Limit RangesTable 8: Horizontal Pod Autoscaling (HPA)Table 9: Vertical Pod Autoscaling (VPA)Table 10: Cluster AutoscalingTable 11: cgroups (Control Groups)Table 12: Node Resource AllocationTable 13: Node Eviction and PreemptionTable 14: Pod OverheadTable 15: Scheduling and PlacementTable 16: Bin Packing and Scheduler ScoringTable 17: Monitoring and MetricsTable 18: Docker Resource LimitsTable 19: Docker Compose Resource LimitsTable 20: Extended Resources and Custom MetricsTable 21: Cost Optimization and FinOpsTable 22: Advanced Performance TuningTable 23: Resource Policy EnforcementTable 24: Multi-Tenancy and IsolationTable 25: Workload RebalancingTable 26: Container Resource Anti-PatternsTable 27: Pod Disruption BudgetsTable 28: Cluster-Level Resource Best Practices

Table 1: Resource Units and Specifications

Unit	Example	Description
CPU millicore (m)	`500m` = 0.5 CPU cores	• 1000 millicores equals one full CPU core • fractional requests allowed down to 1m granularity.
CPU core	`2` = 2 full CPU cores	• Represents one physical core or one virtual core depending on node type • equivalent to 2000m.
Mebibyte (MiB)	`256Mi` = 268,435,456 bytes	• Binary unit using base-2 (1 MiB = 1024² bytes) • standard for container memory limits in Kubernetes.
Gibibyte (GiB)	`4Gi` = 4,294,967,296 bytes	• Binary unit using base-2 (1 GiB = 1024³ bytes) • preferred over GB for consistency with OS-level memory accounting.

Table 1: Resource Units and Specifications

Unit	Example	Description
CPU millicore (m)	`500m` = 0.5 CPU cores	• 1000 millicores equals one full CPU core • fractional requests allowed down to 1m granularity.
CPU core	`2` = 2 full CPU cores	• Represents one physical core or one virtual core depending on node type • equivalent to 2000m.
Mebibyte (MiB)	`256Mi` = 268,435,456 bytes	• Binary unit using base-2 (1 MiB = 1024² bytes) • standard for container memory limits in Kubernetes.
Gibibyte (GiB)	`4Gi` = 4,294,967,296 bytes	• Binary unit using base-2 (1 GiB = 1024³ bytes) • preferred over GB for consistency with OS-level memory accounting.