Three fleets pinned the same tag under three different digests, which is how a
roll ships old bytes under a new name. The pin is what the CD plane reconciles,
so it is set once — one tag, one digest, every fleet, one commit — and the three
applications are synced together.
Then the fleets drain in parallel with each other and one pod at a time within
themselves. The StatefulSets are OnDelete on purpose: five validators restarting
together take the chain below α and halt it. The estate moves in one motion; the
validators of one chain do not.
A pod is back when it answers its own C-Chain RPC. Not when it reads Ready,
which these fleets never do, and not from a height alone, which an unstarted pod
does not answer and which therefore reads as a lagging one.
Co-authored-by: Hanzo Dev <[email protected]>
zeekayandHanzo Dev
e41e636036