n1-highmem-32 as a GKE node
32 vCPU208 GiBx86_64Google Cloud us-central1N1 High Memory 32
Where the n1-highmem-32 goes
Default GKE setup: GKE ≤ 1.36.
CPU31.65 of 32 vCPU left for your pods
Memory196.69 GiB of 208 GiB left for your pods
your podsDaemonSets (200m, 300 MiB assumed)kubelet reservedeviction
110max pods per node
$1,381.78on demand / month · $1.89/h
$787.26spot / month (varies)
n1-highmem-32 GKE max pods and allocatable memory — quick answers
- How many pods can a n1-highmem-32 run as a node with GKE ≤ 1.36? Up to 110; kubelet keeps 11282 MiB of memory and 150m CPU, leaving 196.98 GiB and 31.85 vCPU for pods.
- How many pods can a n1-highmem-32 run as a node with GKE 1.37+ (Container-Optimized OS)? Up to 110; kubelet keeps 2250 MiB of memory and 150m CPU, leaving 205.80 GiB and 31.85 vCPU for pods.
- How many 500m / 1 GiB pods fit? 63 per node after DaemonSets; 1 nodes for 10 replicas, about $1,381.78/month on demand.
What kubelet reserves on n1-highmem-32
| Setup | Max pods | kube-reserved CPU | Memory reserved + eviction | Allocatable CPU | Allocatable memory | Memory usable |
|---|---|---|---|---|---|---|
| GKE ≤ 1.36 tiered memory reservation | 110 | 150m | 11182 Mi + 100 Mi | 31.85 | 196.98 GiB | 94.7% |
| GKE 1.37+ (Container-Optimized OS) 15 MiB × max pods + 500 MiB, CPU capped at 1 vCPU | 110 | 150m | 2150 Mi + 100 Mi | 31.85 | 205.80 GiB | 98.9% |
How these numbers are computed: reservation formulas. Check a live node with kubectl describe node → Allocatable.
How many pods fit on one n1-highmem-32
Assumes DaemonSets (CNI, kube-proxy, log and metrics agents) request 200m CPU, 300 Mi and 3 pods per node. Try your own numbers in the node calculator.
| Pod requests (CPU / memory) | GKE ≤ 1.36 | GKE 1.37+ (Container-Optimized OS) | $ per pod / month |
|---|---|---|---|
| 100m / 128 Mi | 107 | 107 | $12.91 |
| 250m / 256 Mi | 107 | 107 | $12.91 |
| 250m / 512 Mi | 107 | 107 | $12.91 |
| 500m / 512 Mi | 63 | 63 | $21.93 |
| 500m / 1024 Mi | 63 | 63 | $21.93 |
| 1000m / 1024 Mi | 31 | 31 | $44.57 |
| 1000m / 2048 Mi | 31 | 31 | $44.57 |
| 2000m / 4096 Mi | 15 | 15 | $92.12 |
| 4000m / 8192 Mi | 7 | 7 | $197.40 |
Similar GKE node types
| Type | vCPU | GiB | Alloc CPU | Alloc memory | Max pods | $/month | $ per alloc GiB |
|---|---|---|---|---|---|---|---|
| c4-highmem-32 | 32 | 248 | 31.85 | 236.18 GiB | 110 | $1,522.36 | $6.45 |
| c4-highmem-32-lssd | 32 | 248 | 31.85 | 236.18 GiB | 110 | $1,822.36 | $7.72 |
| c4d-highmem-32 | 32 | 252 | 31.85 | 240.10 GiB | 110 | $1,454.42 | $6.06 |
| c4d-highmem-32-lssd | 32 | 252 | 31.85 | 240.10 GiB | 110 | $1,574.42 | $6.56 |
| c3d-highmem-30 | 30 | 240 | 29.86 | 228.34 GiB | 110 | $1,341.05 | $5.87 |
| c3d-highmem-30-lssd | 30 | 240 | 29.86 | 228.34 GiB | 110 | $1,401.05 | $6.14 |
| n4a-highmem-32 | 32 | 256 | 31.85 | 244.02 GiB | 110 | $1,180.61 | $4.84 |
| n4d-highmem-32 | 32 | 256 | 31.85 | 244.02 GiB | 110 | $1,298.58 | $5.32 |
Closest match on other clouds
| Type | vCPU | GiB | Alloc CPU | Alloc memory | Max pods | $/month | $ per alloc GiB |
|---|---|---|---|---|---|---|---|
| e32psv5 | 32 | 208 | 31.58 | 202.97 GiB | 250 | $1,177.49 | $5.80 |
| e32pdsv5 | 32 | 208 | 31.58 | 202.97 GiB | 250 | $1,345.39 | $6.63 |
| ec32asv5 | 32 | 192 | 31.58 | 186.97 GiB | 250 | $1,319.84 | $7.06 |
| ec32adsv5 | 32 | 192 | 31.58 | 186.97 GiB | 250 | $1,530.08 | $8.18 |
| ec32asv6 | 32 | 192 | 31.58 | 186.97 GiB | 250 | $1,531.54 | $8.19 |
| ec32adsv6 | 32 | 192 | 31.58 | 186.97 GiB | 250 | $1,865.88 | $9.98 |