When running heavily CPU-bound workloads where memory requests are minimal compared to CPU requests, Karpenter provisions standard instance types (e.g., GCP c4a) that pack requested CPU near 100% while leaving allocated memory utilization/requests under 20%.
Consolidation does not replace these nodes because no smaller standard instance fits the CPU requirements, and Karpenter does not prioritize high-CPU/compute-optimized instance families when calculating optimal node replacement.
- CPU Requests: ~99% (e.g., 71306m / 72000m)
- Memory Requests: ~15% - 22%
- Consolidation state: Idle / No action taken
Improve consolidation heuristics or instance-selection logic to prioritize high-CPU / low-memory instance families when memory request percentage across pods is disproportionately low compared to CPU requests.
When running heavily CPU-bound workloads where memory requests are minimal compared to CPU requests, Karpenter provisions standard instance types (e.g., GCP
c4a) that pack requested CPU near 100% while leaving allocated memory utilization/requests under 20%.Consolidation does not replace these nodes because no smaller standard instance fits the CPU requirements, and Karpenter does not prioritize high-CPU/compute-optimized instance families when calculating optimal node replacement.
Improve consolidation heuristics or instance-selection logic to prioritize high-CPU / low-memory instance families when memory request percentage across pods is disproportionately low compared to CPU requests.