WHAT

The stimzi bundle version is currently used to control the rollout of all changes that need blast radius.

WHY

This coupling creates situations where unrelated changes are being rolled together and potentially necessitates creating artificial strimzi versions, just to control behavior in the fleetshard

HOW

Create separate mechanisms by which things like scheduling changes can be rolled in separately from the strimzi bundle version. To be done in a similar manner as we have been, this could be something like a separate version flag in the managedkafka specifically for the fleetshard.

This should also be a topic for the architecture group as other services should have a similar issue. As part of a broader discussion we have talked before about the eventually need for all such upgrade processes to be more automated - that is the FSO based upon some health monitoring should be able to process some rollouts on its own.

cc keithbwall rhn-engineering-rareddy medgar@redhat.com mchitimb-1