You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
migtools/kubevirt-datamover-controller is adding a --max-concurrent-data-movers flag (int, default 0 = unlimited) to gate concurrent active DataUploads/DataDownloads, tracked in migtools/kubevirt-datamover-controller#84 (sub-issues #174 DU side, #175 DD side).
This tracking issue covers exposing that flag through spec.configuration.kubevirtDatamover.maxConcurrentDataMovers in the DPA CRD, mirroring maxIncrementalBackups/staleDataUploadThreshold in that same config section.
How to test the changes made
Set spec.configuration.kubevirtDatamover.maxConcurrentDataMovers on a DPA and verify the oadp-kubevirt-datamover-controller-manager deployment's manager container gets --max-concurrent-data-movers=<N>.
Why the changes were made
migtools/kubevirt-datamover-controller is adding a
--max-concurrent-data-moversflag (int, default 0 = unlimited) to gate concurrent active DataUploads/DataDownloads, tracked in migtools/kubevirt-datamover-controller#84 (sub-issues #174 DU side, #175 DD side).This tracking issue covers exposing that flag through
spec.configuration.kubevirtDatamover.maxConcurrentDataMoversin the DPA CRD, mirroringmaxIncrementalBackups/staleDataUploadThresholdin that same config section.How to test the changes made
Set
spec.configuration.kubevirtDatamover.maxConcurrentDataMoverson a DPA and verify theoadp-kubevirt-datamover-controller-managerdeployment'smanagercontainer gets--max-concurrent-data-movers=<N>.Blocked on migtools/kubevirt-datamover-controller#174 and #175 landing upstream before the flag exists on the controller binary.
Note
Responses generated with Claude