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

Stop zood-mv declaring a version behind the fleet it runs

Browse Source 
Declared v1.36.58 against v1.36.68 running. This is the one that could have
taken the chain down: zood-mv is the only luxd StatefulSet on RollingUpdate with
podManagementPolicy Parallel, so a sync would not have rolled back gradually —
it would have restarted all five Zoo validators at once, at an older version.

Two facts make that unrecoverable rather than merely bad. luxd waits for peers
before it listens, so a whole fleet restarting together deadlocks: every node is
waiting for a node that is also waiting. And N=5 with alpha=4 means one node
down is already a de-facto halt, so there is no slack to absorb it.

The value is copied from the live StatefulSet. Nothing changes; the app simply
stops carrying an instruction that would have been obeyed.

Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
zeekay
2026-09-03 21:32:51 -07:00
committed by Hanzo AI
co-authored by Hanzo Dev
parent d37876f960
commit 1750b3b263
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deploy/zoo-mainnet/zood-mv.yaml
+1 -1
View File
@@ -7,7 +7,7 @@ selectorLabels:
containerName: zood
image:
repository: ghcr.io/luxfi/node
tag: v1.36.58
tag: v1.36.68
digest: sha256:175ef334c44575dc0f2a4abdaf0cc27b04e601a4494a93f4d3ff41db3170e1e1
pullPolicy: IfNotPresent
command: