zoo/universe
2
0
Fork 0
Code Issues Pull Requests Releases Activity

fix(zoo-mainnet): lower validator requests to fit zoo-nodes pool

Browse Source 
zoo-mainnet zoo-chain-0 was stuck Pending (FailedScheduling: Insufficient
memory on 0/5 nodes). Its validator memoryRequest was an anomalous 8Gi while
the zoo-nodes pool (s-4vcpu-8gb-amd) has only ~6.26Gi allocatable per node, so
a single 8Gi-request pod could never schedule. cpuRequest of 2 also tripped
Insufficient cpu on a packed node.

Lower requests to match zoo-testnet (memoryRequest 4Gi, cpuRequest 1) so all 5
replicas can co-schedule. Limits stay generous (memoryLimit 16Gi, cpuLimit 8)
for mainnet headroom.
This commit is contained in:
hanzo-dev
2026-06-23 19:01:11 +00:00
parent ab71a3dabe
commit 45ea50e53d
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
k8s/zoo-mainnet/network-patch.yaml
+5 -2
View File
@@ -18,9 +18,12 @@ spec:
tag: v1.30.40
pullPolicy: IfNotPresent
resources:
cpuRequest: "2"
# requests sized to fit the zoo-nodes pool (s-4vcpu-8gb-amd, ~6.26Gi /
# ~3.8 vCPU allocatable per node); matches zoo-testnet so 5 replicas can
# co-schedule. Limits stay generous (16Gi / 8 vCPU) for mainnet headroom.
cpuRequest: "1"
cpuLimit: "8"
memoryRequest: 8Gi
memoryRequest: 4Gi
memoryLimit: 16Gi
storage:
storageClass: do-block-storage