Tomáš Nožička

(I don't think this was supported before in helm, so it isn't a regression/bug. It also nicely shows that with CRs it just makes more sense to use them directly...

currently and historically you can't override scylla args set by the operator. this is coupled a lot to the startup scripts in the scylla image. we may get a better...

maybe some (not this one) even shouldn't be let to be overwritten as they are essential to how we set up scylla and its relation to other kube objects

admission can't be restricted retrospectively not to break backwards compatibility (that's why it is important to get it right the first time)

This is not allowed. Objects valid in the past have to be able to be created again. Also storage migration must keep working so you must be able to go...

I think the approach looks viable overall, needs a few details that should be flashed out in the proposal.

> Which releases do you want me to bump? v1.7 only? You are shipping your changes to master, which is what's gonna be in 1.8 so you need to make...

I don't wanna mess with multiple API version for a one timer. Given we have already claimed 1.7 will work on >=1.20 we should update it to `>=1.20 &&

let's do it in this PR, the rest lgtm

> Should I apply the upper bound to earlier releases too? If so, is