Hi,
first of all I think that we should not reinvent the wheel here. I
think that I am not far from the truth when I say that Orange's
operator is the most mature one when it comes to features and the most
battle-tested. I have not checked how it is done in details internally
yet but I am
Hi all,
We at Orange would love to be included in these talks about a unique Kubernetes
operator for Cassandra.
It comes a bit late for us as we have spent a couple of years on ours and are
close to running it in production but moving to a community supported one will
be better for
Sure. Let me figure out some timing and propose some times.
On Tue, Mar 31, 2020 at 5:15 PM Nate McCall wrote:
> Given the large portion of work that's been done in EU by the Orange folks
> vs. that of PST and APAC, I think this might be one for which we do two
> versions: PST morning and
*Thanks for starting this thread Ben! Definitely agree that having a single
project-owned Kubernetes operator for Cassandra is preferred over a
fragmented ecosystem. I'll echo the same sentiment based on conversations
that it appears the community is eager to share experiences and
implementations
Hi Ben!
Totally agree. We should collaborate on a unified operator and I think as
deployment on k8s becomes more and more prevalent we need to have
distributed testing in k8s.
To that end we are working on OSS releasing our distributed testing service
we've developed over the years to make this
Hi All
With the announcement of a C* Sidecar and K8s operator from Datastax
(congrats btw), Jake and Stefan discussed moving to a more
standardised/unified implementation of an Apache Cassandra operator for
Kubernetes. Based on discussions with other folks either using our
operator,
