Remove the CassandraDatacenter spec from CassandraBackup objects

[sync-by-unito[bot]]

CassandraBackup resources shouldn’t store the CassandraDatacenter spec anymore but rather the topology object generated by Medusa. This object will contain the list of live nodes at the time of the backup along with their token assignments. Sample topology object:

{"ip-179-31-16-38.us-west-2.compute.internal": {"tokens": [-1051417974279770378, -112095142485141927, 9217379683620055011, 939597040143840721], "is_up": true}, 
 "ip-179-31-23-54.us-west-2.compute.internal": {"tokens": [-1080182033668782299, -1156652990105327691, 9134535641516355167, 9216775765860996507], "is_up": true}, 
 "ip-179-31-30-139.us-west-2.compute.internal": {"tokens": [-1018393144648419592, -1342532530495729638, 8846603596658721956, 8849342512812637165], "is_up": true}}

The CRD should also contain the storage bucket prefix, which is controlled by the namespace name.

┆Issue is synchronized with this Jiraserver Feature by Unito ┆Epic: Remote Cluster Restore ┆Issue Number: K8SSAND-522 ┆Priority: Medium

[sync-by-unito[bot]]

➤ Jeff DiNoto commented:

• Involves the removal of content from the definition and the addition of topology information
  • Will require an update to the gRPC operation to provide topology information in addition to existing backup information