Re: Kubernetes Operator: Can We Preserve CassKop's Flexibility?

Hey Tom, You make some great points. I agree that there is an ecosystem of tooling surrounding cass-operator, but those tools are narrowly focused on particular tasks. Ideally, as community iniatives like CEP-1 graduate, t

Re: Supported upgrade path for 4.0

> "3.11 performs close to parity with 2.1/2.2. 3.0 does not. If we recommend > people upgrade from 2.1 -> 3.0 -> 4.0, we are asking them to have a cluster > in a regressed performance state for potentially months as they execute > their upgrade." > > Did I get anything wrong here Mick? ^ > That's

Re: Supported upgrade path for 4.0

Hm. We have a wrinkle that's thankfully testable. I've been talking back and forth w/Mick about his and the TLP team's experience upgrading clusters to 3.0 vs. upgrading to 3.11. The observations and assertion: 3.0 has performance regressions from 2.1 that were fixed through the tick-tock line as

Re: Supported upgrade path for 4.0

This sounds eminently sensible to me. On 09/10/2020, 19:42, "Joshua McKenzie" wrote: Fair point on uncertainties and delaying decisions until strictly required so we have more data. I want to nuance my earlier proposal and what we document (sorry for the multiple messages; my t