The version-check initContainer and version-check-term container should use the Patch operation instead of Update to avoid race conditions that can result in errors logs such as:
failed to patch status: Operation cannot be fulfillfed on cosmosfullnodes.cosmos.strange.love: the object has been modified
This is only seen intermittently, and the instance will automatically recover on the next restart.
Since the version check is a synchronous operation per instance, we don't need to worry about multiple concurrent writers to the status.height of the specific instance. The RPC status.height updates will only occur after this when the node is started.
The
version-checkinitContainer andversion-check-termcontainer should use thePatchoperation instead ofUpdateto avoid race conditions that can result in errors logs such as:This is only seen intermittently, and the instance will automatically recover on the next restart.
Since the version check is a synchronous operation per instance, we don't need to worry about multiple concurrent writers to the status.height of the specific instance. The RPC status.height updates will only occur after this when the node is started.