Maintenance Job only uses the first element of the LoadAffinity array from the ConfigMap. (#9494)

Signed-off-by: Xun Jiang <xun.jiang@broadcom.com>

changelogs/unreleased/9494-blackpiglet

@@ -0,0 +1 @@
+Maintenance Job only uses the first element of the LoadAffinity array

pkg/repository/maintenance/maintenance.go

@@ -671,7 +671,8 @@ func buildJob(
 	}
 
 	if config != nil && len(config.LoadAffinities) > 0 {
-		affinity := kube.ToSystemAffinity(config.LoadAffinities)
+		// Maintenance job only takes the first loadAffinity.
+		affinity := kube.ToSystemAffinity([]*kube.LoadAffinity{config.LoadAffinities[0]})
 		job.Spec.Template.Spec.Affinity = affinity
 	}
 

site/content/docs/main/repository-maintenance.md

@@ -77,19 +77,6 @@ data:
       },
       "keepLatestMaintenanceJobs": 1,
       "loadAffinity": [
-        {
-          "nodeSelector": {
-            "matchExpressions": [
-              {
-                "key": "cloud.google.com/machine-family",
-                "operator": "In",
-                "values": [
-                  "e2"
-                ]
-              }
-            ]
-          }
-        },
         {
           "nodeSelector": {
             "matchExpressions": [
@@ -119,10 +106,10 @@ data:
     }
 EOF
 ```
-This sample showcases two affinity configurations:
-- matchLabels: maintenance job runs on nodes with label key `cloud.google.com/machine-family` and value `e2`.
+Notice: although loadAffinity is an array, Velero only takes the first element of the array.
+
+This sample showcases how to use affinity configuration:
 - matchLabels: maintenance job runs on nodes located in `us-central1-a`, `us-central1-b` and `us-central1-c`.
-The nodes matching one of the two conditions are selected.
 
 To create the configMap, users need to save something like the above sample to a json file and then run below command:
 ```