Fix: Enable throttling parameters in BackupRepository repositoryConfig

The `uploadBytes`, `downloadBytes`, and other throttling parameters specified in BackupRepository's `repositoryConfig` were being silently filtered out and not applied to Kopia repositories. This occurred because these parameters were missing from the whitelist in `getStorageVariables()`.

**Code:**
- Added throttling options to the valid parameters whitelist in `pkg/repository/provider/unified_repo.go`:
  - `uploadBytes` - upload bandwidth throttling (bytes/sec)
  - `downloadBytes` - download bandwidth throttling (bytes/sec)
  - `readOPS` - read operations throttling (ops/sec)
  - `writeOPS` - write operations throttling (ops/sec)
  - `listOPS` - list operations throttling (ops/sec)

**Documentation:**
- Updated `site/content/docs/main/backup-repository-configuration.md` with throttling parameters descriptions and examples

**Tests:**
- Added test case in `pkg/repository/provider/unified_repo_test.go` to verify throttling parameters are properly passed through

```yaml
apiVersion: velero.io/v1
kind: BackupRepository
spec:
  repositoryConfig:
    uploadBytes: "838860800"    # ~800 MB/s
    downloadBytes: "838860800"  # ~800 MB/s
```

These parameters are now properly applied to Kopia during file system backups performed by node-agent.

Signed-off-by: Andrei Kvapil <[email protected]>

Author: kvaps

pkg/repository/provider/unified_repo.go

@@ -586,6 +586,11 @@ func getStorageVariables(backupLocation *velerov1api.BackupStorageLocation, repo
 		validParams := []string{
 			udmrepo.StoreOptionCacheLimit,
 			udmrepo.StoreOptionKeyFullMaintenanceInterval,
+			udmrepo.ThrottleOptionReadOps,
+			udmrepo.ThrottleOptionWriteOps,
+			udmrepo.ThrottleOptionListOps,
+			udmrepo.ThrottleOptionUploadBytes,
+			udmrepo.ThrottleOptionDownloadBytes,
 		}
 		for _, param := range validParams {
 			if v, found := backupRepoConfig[param]; found {

pkg/repository/provider/unified_repo_test.go

@@ -460,6 +460,37 @@ func TestGetStorageVariables(t *testing.T) {
 				"cacheLimitMB": "1000",
 			},
 		},
+		{
+			name: "fs with throttle config",
+			backupLocation: velerov1api.BackupStorageLocation{
+				Spec: velerov1api.BackupStorageLocationSpec{
+					Provider: "velero.io/fs",
+					Config: map[string]string{
+						"fspath": "fake-path",
+						"prefix": "fake-prefix",
+					},
+				},
+			},
+			repoBackend: "fake-repo-type",
+			repoConfig: map[string]string{
+				udmrepo.ThrottleOptionUploadBytes:   "838860800",
+				udmrepo.ThrottleOptionDownloadBytes: "838860800",
+				udmrepo.ThrottleOptionReadOps:       "100",
+				udmrepo.ThrottleOptionWriteOps:      "100",
+				udmrepo.ThrottleOptionListOps:       "50",
+			},
+			expected: map[string]string{
+				"fspath":        "fake-path",
+				"bucket":        "",
+				"prefix":        "fake-prefix/fake-repo-type/",
+				"region":        "",
+				"uploadBytes":   "838860800",
+				"downloadBytes": "838860800",
+				"readOPS":       "100",
+				"writeOPS":      "100",
+				"listOPS":       "50",
+			},
+		},
 	}
 
 	for _, tc := range testCases {

site/content/docs/main/backup-repository-configuration.md

@@ -31,7 +31,9 @@ data:
   <kopia>: |
     {
       "cacheLimitMB": 2048,
-      "fullMaintenanceInterval": "fastGC"
+      "fullMaintenanceInterval": "fastGC",
+      "uploadBytes": "838860800",
+      "downloadBytes": "838860800"
     }
   <other-repository-type>: |
     {
@@ -59,5 +61,15 @@ Per kopia [Maintenance Safety](https://kopia.io/docs/advanced/maintenance/#maint
 
 On the other hand, the not-in-use data will be deleted permanently after the full maintenance, so shorter full maintenance intervals may weaken the data safety if they are used incorrectly.
 
+`uploadBytes`: specifies the maximum upload speed in bytes per second for the repository. This can be used to throttle the upload bandwidth. The value should be specified as a string representing bytes per second (e.g., "838860800" for ~800 MB/s). This parameter applies during repository operations that write data.
+
+`downloadBytes`: specifies the maximum download speed in bytes per second for the repository. This can be used to throttle the download bandwidth. The value should be specified as a string representing bytes per second (e.g., "838860800" for ~800 MB/s). This parameter applies during repository operations that read data.
+
+`readOPS`: specifies the maximum number of read operations per second. This can be used to throttle the rate of read operations to the storage backend.
+
+`writeOPS`: specifies the maximum number of write operations per second. This can be used to throttle the rate of write operations to the storage backend.
+
+`listOPS`: specifies the maximum number of list operations per second. This can be used to throttle the rate of list operations to the storage backend.
+
 [1]: file-system-backup.md
 [2]: csi-snapshot-data-movement.md