When running Cassandra on Kubernetes today I use a StatefulSet, where I can configure multiple containers. That way I can run both the Cassandra image and a custom image (as a sidecar) in the same Pod.
Is it possible to do the same/similar thing when using the Kubernetes Operator for Cassandra (cass-operator)?
The team responsible for releasing the Cassandra operator also released a management API sidecar for Cassandra which you might be interested in.
I'm going to reach out internally to the team and get them to respond directly to your question. Cheers!
Hi @ted.petersson_164115 this is exactly how things work.
More information here from slides 43 to 47
Next livestream for this workshop will be june 11th you should come and try with us, it is totally free, simply a live on youtube. All exercises and yaml in the sane github repo i showed you.
Ok, A can see the Management API SideCar. But my question was really if I could (via CRD-CassandraDataCenter config) could provide my own custom sidecar?
Since I already have one today for handling backup/restore... I was wondering if I could reuse that image/logic when using cass-operator?
Operator is looking over PODS for `readyness` and `liveness` on dedicated port/path. As long as you have the same specifications you could be ok.
Nice. Is it possible to have a custom sidecar image without forking the project?
I see that the Cassandra serverImage can be configured like this:
https://github.com/datastax/cass-operator/tree/master/docs/user#using-a-specific-image
Is it possible to configure a custom sidecar image in a similar way? I.e. adding an "extra" custom sidecar.
Or "overriding" the Management API SideCar to run your own image?
With version 1.2.0 of cass-operator there is now a PodTemplateSpec parameter in the CRD which allows for specifying additional side car processes per pod.
8 People are following this question.
