[BUG] Modification to ClusterState Object lacks backward compatiblility in remote publication mode #19843
Description
Describe the bug
In transport cluster state publication since active cluster manager sends cluster state updates individually to all nodes in the cluster, when new fields are introduced to cluster state it is easier to handle backward compatibility by serializing fields based on the version of the node receiving the update and hence different nodes in will receive the version of the cluster state that they understand. Whereas, in remote publication the cluster state serialized only once and uploaded to remote, which thereby limits the active cluster manager from creating different versions of the cluster state for the different node versions and can fail the remote cluster download in such cases because of unread data.
We need to explore and introduce a mechanism for maintaining the backward compatibility that allows ClusterState class modification in remote publication.
Related component
Cluster Manager
To Reproduce
N/A
Expected behavior
Support for making modifications to ClusterState class with backward compatibility in remote publication mode.