Fade out to another Cassandra operator

[bygui86]

Hi guys

on the main page is written that the operator is at its sunset phase of life and it's better move to another one (Orange or DataStax).

First of all thank you for your hard work and sad that such a good tool is leaving.
Now coming to the main points...

Is there a migration process? Some tips to migrate from an operator to another? Some advises to migrate data from a cassandra operated cluster to another one?

What about compatibility between instaclust/cassandra-operator and the other ones?

Maybe it's a stupid question but...
having a instaclust/cassandra-operator cluster already up and running since long time, could I scale it down and scale up another cluster operated by Orange or DataStax using the very same PVCs?

Thanks in advance for any help

[smiklosovic]

Hi,

the best thing for migration would be to backup all your data by what this operator offers, recreate whole schema on the target cluster and restore it there. It should be possible, maybe you hit some cornercases but it should be doable.

You should have same topology (same number of nodes) and same tokens for each node so once you restore data, node by node, it will fit - tokens-wise.

By the way, Orange (CassKop) is using Icarus / Esop as their backup / restore solution. We were helping them with the integration of our tooling so you should just backup with Icarurs / Esop in this operator (you probably know how to do that already) and then you restore it in CassKop - again by means of Icarus which they are using :) so your backup should be restorable in a different cluster because restoration process is using Icarus again.

Maybe there will be some difference in the version of Icarus this operator is running and the one they are using - having this one older - but lets see if it does not work anyway and if there are some discrepancies I can spend some time aligning the version with CassKop, it should be pretty straightforward.

[bygui86]

@smiklosovic thank you for the tips