Charon clusters can agree on supported versions #1380
Comments
obol-bulldozer bot
pushed a commit
that referenced
this issue
Nov 4, 2022
Adds the `infosync` component that prioritised cluster supported versions. Also add the `priority.Component` that wraps the prioritiser to hide protobuf types and do signing. category: feature ticket: #1380
Merged
obol-bulldozer bot
pushed a commit
that referenced
this issue
Nov 7, 2022
Wires the priority protocol and add integration test. category: feature ticket: #1380
corverroos
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem to be solved
We introduce a breaking change. We tell people to update. For a period of time, 2 clients will be on the old version and 2 clients will be on the new version, so we will be offline. Step 1 to solve this is to agree on what versions are supported by the cluster.
Proposed solution
Use prioritise to choose a version that ever speaks.
Out of Scope
Enabling/Disabling features based on prioritised versions.
The text was updated successfully, but these errors were encountered: