This is an allternative for #1469, removing the Placemnt[Rule] changes.
When disabling DR we planned to keep OCM scheduling disabled in all cases, since a Placment[Rule] may be managed by GitOps and any change we made may be overridden.
Enabling OCM scheduling is not only not needed, it is risky and we should actually warn users not to do this, since OCM is does not really support statefull workloads. Changing the placement of such workloads delete the current data and start with a fresh PVCs on new location.
From user point of view, this disabling DR is still single step - deleting the drpc. If they want to start managed the application with OCM (unlikely for stateful application), users will have to make sure the Placment[Rule] matches the current location.
This is an allternative for #1469, removing the Placemnt[Rule] changes.
When disabling DR we planned to keep OCM scheduling disabled in all cases, since a Placment[Rule] may be managed by GitOps and any change we made may be overridden.
Enabling OCM scheduling is not only not needed, it is risky and we should actually warn users not to do this, since OCM is does not really support statefull workloads. Changing the placement of such workloads delete the current data and start with a fresh PVCs on new location.
From user point of view, this disabling DR is still single step - deleting the drpc. If they want to start managed the application with OCM (unlikely for stateful application), users will have to make sure the Placment[Rule] matches the current location.
Related ocm-ramen-samples changes:
Fixes #1441