n2d-highmem-2 as a GKE node
2 vCPU16 GiBx86_64Google Cloud us-central1N2D High Memory 2
Where the n2d-highmem-2 goes
Default GKE setup: GKE ≤ 1.36.
CPU1.73 of 2 vCPU left for your pods
Memory13.01 GiB of 16 GiB left for your pods
your podsDaemonSets (200m, 300 MiB assumed)kubelet reservedeviction
110max pods per node
$83.21on demand / month · $0.1140/h
$42.37spot / month (varies)
n2d-highmem-2 GKE max pods and allocatable memory — quick answers
- How many pods can a n2d-highmem-2 run as a node with GKE ≤ 1.36? Up to 110; kubelet keeps 2762 MiB of memory and 70m CPU, leaving 13.30 GiB and 1.93 vCPU for pods.
- How many pods can a n2d-highmem-2 run as a node with GKE 1.37+ (Container-Optimized OS)? Up to 110; kubelet keeps 2250 MiB of memory and 70m CPU, leaving 13.80 GiB and 1.93 vCPU for pods.
- How many 500m / 1 GiB pods fit? 3 per node after DaemonSets; 4 nodes for 10 replicas, about $332.82/month on demand.
What kubelet reserves on n2d-highmem-2
| Setup | Max pods | kube-reserved CPU | Memory reserved + eviction | Allocatable CPU | Allocatable memory | Memory usable |
|---|---|---|---|---|---|---|
| GKE ≤ 1.36 tiered memory reservation | 110 | 70m | 2662 Mi + 100 Mi | 1.93 | 13.30 GiB | 83.1% |
| GKE 1.37+ (Container-Optimized OS) 15 MiB × max pods + 500 MiB, CPU capped at 1 vCPU | 110 | 70m | 2150 Mi + 100 Mi | 1.93 | 13.80 GiB | 86.3% |
How these numbers are computed: reservation formulas. Check a live node with kubectl describe node → Allocatable.
How many pods fit on one n2d-highmem-2
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 | 17 | 17 | $4.89 |
| 250m / 256 Mi | 6 | 6 | $13.87 |
| 250m / 512 Mi | 6 | 6 | $13.87 |
| 500m / 512 Mi | 3 | 3 | $27.74 |
| 500m / 1024 Mi | 3 | 3 | $27.74 |
| 1000m / 1024 Mi | 1 | 1 | $83.21 |
| 1000m / 2048 Mi | 1 | 1 | $83.21 |
| 2000m / 4096 Mi | 0 | 0 | — |
| 4000m / 8192 Mi | 0 | 0 | — |
Similar GKE node types
| Type | vCPU | GiB | Alloc CPU | Alloc memory | Max pods | $/month | $ per alloc GiB |
|---|---|---|---|---|---|---|---|
| e2-highmem-2 | 2 | 16 | 1.93 | 13.30 GiB | 110 | $65.99 | $4.96 |
| n4a-highmem-2 | 2 | 16 | 1.93 | 13.30 GiB | 110 | $73.79 | $5.55 |
| n4d-highmem-2 | 2 | 16 | 1.93 | 13.30 GiB | 110 | $81.16 | $6.10 |
| c4a-highmem-2 | 2 | 16 | 1.93 | 13.30 GiB | 110 | $86.05 | $6.47 |
| n4-highmem-2 | 2 | 16 | 1.93 | 13.30 GiB | 110 | $86.88 | $6.53 |
| c2d-highmem-2 | 2 | 16 | 1.93 | 13.30 GiB | 110 | $89.40 | $6.72 |
| n2-highmem-2 | 2 | 16 | 1.93 | 13.30 GiB | 110 | $95.64 | $7.19 |
| c4d-highmem-2 | 2 | 15 | 1.93 | 12.40 GiB | 110 | $88.85 | $7.16 |