.Deleting the internal `VolumeReplicaitonGroup` resource from where a workload failed over or relocated from no longer causes errors Due to a bug in the disaster recovery (DR) reconciler, during deletion of the internal `VolumeReplicaitonGroup` resource on a managed cluster, from where a workload failed over or relocated from, a persistent volume claim (PVC) was attempted to be protected. The resulting cleanup operation did not complete and would report the `PeerReady` condition on the `DRPlacementControl` for the application to be `False`. This meant the application that was failed over or relocated, could not be relocated or failed over again because the `DRPlacementControl` resource was reporting its `PeerReady` condition as `False`. With this update, during deletion of the internal `VolumeReplicationGroup` resource, a PVC is not attempted to be protected again, thereby avoiding the issue of a stalled cleanup. This results in `DRPlacementControl` reporting `PeerReady` as `True` post auto completion of the cleanup.