I've been following the discussion about Kubernetes operators with a great
deal of interest. At New Relic, we're about to move our Cassandra Clusters
from bare-metal hosts in our datacenters to Kubernetes clusters in AWS, so
we've been looking closely at the current operators.
Our goals:
* Don't
Thanks for taking action on that Scott.
Just want to ping the list here as a reminder for everyone: 48 hours to go!
Reminder: *anything you think is crucial for us to get in before 4.0 GA,
please remove the 4.0-triage FixVersion from the tickets by Friday*.
Thanks.
On Tue, Oct 06, 2020 at 11:5
Updated the link to exclude resolved; down to 27 remaining (was 32)
https://issues.apache.org/jira/issues/?jql=project%20%3D%20cassandra%20and%20fixversion%20%3D%204.0-triage%20and%20status%20!%3D%20Resolved
> On Oct 7, 2020, at 12:16 PM, Joshua McKenzie wrote:
>
> Thanks for taking action on t
Thank you Tom for your support, as one of the main contributors of CassKop I’m
happy to see that the efforts we put in it to try to support as many
configurations as possible is well appreciated.
When we first started to talk about creating a kubernetes operator we always
mentioned the features
Done https://issues.apache.org/jira/browse/CASSANDRA-16199
Best
—
Cyril Scetbon
> On Sep 1, 2020, at 12:22 PM, Joshua McKenzie wrote:
>
> Go for it!
>
> On Mon, Aug 31, 2020 at 10:23 PM Cyril Scetbon
> wrote:
>
>> Hey guys,
>>
>> Experimenting with Cassandra 4.0 I’m seeing that when CASSAND
