Can operator be expanded to allow for ScyllaDB deployment?
Opened this issue · 2 comments
ScyllaDB is a drop-in replacement for Cassandra. Does it require more on the operator side than just a few small changes?
Hey @iandebeer, we have a few parameters that are available in the docker image we built, and we use a Jolokia agent to interact with Cassandra nodes. As long as those variables and the Jolokia agent are available in the scyllaDB image it should not be a problem.
They are also working on a side car in Cassandra 4 which will led us to a replacement of our jolokia call. Could be a problem to support ScyllaDB in the futur. Or we'll need to implement different functions for the pod operations depending on the type of database used.
Take a look at https://github.com/Orange-OpenSource/cassandra-image/blob/master/files/run.sh.
I'm eager to see Cassandra official docker image being released to close that other project.
Hi @iandebeer,
We have changed our architectur and are now using InitContainers to bootstrap our Cassandra docker Image. I've tested it with Scylladb but we need to make use of dedicated bootstrap image i for scylla. This is the bootstrapImage we uses for Cassandra: https://github.com/Orange-OpenSource/cassandra-k8s-operator/tree/master/docker/bootstrap
If you like you can submit a PR for a ScyllaDB Bootstrap image :)