In order to support Operator upgrades, three items are required:

1. Operator code needs to be updated to ensure that upgrades between patch versions only triggers a StatefulSet rolling upgrade instead of a full graceful shutdown. Rebalancing should still be disabled until the operation is complete and we can utilise the "onDelete" strategy to provide further control of the rollout process if required. We can make this explicit by adding a "zero-downtime" upgrade strategy in the CR

1. If the user required zero-downtime upgrades, then they need to full the full upgrade path updating from .0 -> .1 -> .2

1. Ensure that an Operator release exists per Infinispan server release upstream to ensure 2 is possible.