1. Proposed title of this feature request  

   [RFE] Add functionality in Pulp3 to limit/control repo sync speed for Satellite and Capsule.
      
2. What is the nature and description of the request?  

   In Satellite 6.10, there is no option to control the speed at which syncs are performed on Satellite or with Satellite-Capsule sync.

   We have similar feature in Pulp2, we can define max speed in Pulp2.

   Detailed information can be found in https://access.redhat.com/articles/2387381

3. Why does the customer need this? (List the business requirements here)  

   Customer's network team requested to limit traffic to 4 MB/s.
   Currently, as per settings, there is no limit for sync.
   Currently, customer's requirement is for Satellite to Capsule sync but it will be nice if the same feature is added for repositories sync in Satellite as well.

Ultimately Satellite (the application level) is not the correct place to be putting bandwidth limits. Even though it was supported previously, it is a strictly inferior solution compared to setting up an appropriate network traffic shaping policy [0] [1].

Satellite, even if it had complete network awareness between all of its own services, has no awareness of what any other services on the machine or machines on the network might be doing.  The only actor on the machine with that kind of global knowledge and control over networking is the operating system itself.  

[0] https://en.wikipedia.org/wiki/Traffic_shaping
[1] https://octetz.com/docs/2020/2020-09-16-tc/

All this being said, we ought to provide configuration recommendations for low-bandwidth scenarios.  The defaults are not optimized for this and I expect that the default timeout settings in particular would be very much insufficient for systems operating under strict bandwidth limitations.