Upgrade and Rollback

Protocol upgrades require compatible execution and consensus client versions. Read both client release notes, stage images, and upgrade one node at a time behind the load balancer.

Rollback must preserve database compatibility. If a client release performs an irreversible database migration, test restore from snapshot before production rollout.

kubectl -n ethereum rollout status statefulset/geth
kubectl -n ethereum rollout status statefulset/lighthouse

Keep Engine JWT and data volumes unchanged across image rollbacks.