Clarify thirdparty label/annotations on the maintenance jobs

Signed-off-by: Tiger Kaovilai <tkaovila@redhat.com>

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

@@ -155,9 +155,22 @@ Status:
 - `Recent Maintenance` keeps the status of the recent 3 maintenance jobs, including its start time, result (succeeded/failed), completion time (if the maintenance job succeeded), or error message (if the maintenance failed)
 
 ### Others
-Maintenance jobs will inherit the labels, annotations, toleration, nodeSelector, service account, image, environment variables, cloud-credentials etc. from Velero deployment.  
+Maintenance jobs will inherit specific labels, annotations, toleration, nodeSelector, service account, image, environment variables, cloud-credentials etc. from Velero deployment.
+
+For labels, maintenance jobs include:
+- `velero.io/repo-name: <repository-name>` to identify which repository they are maintaining
+- Only [third-party labels][4] from the Velero server deployment that are in the predefined list, currently including:
+  - `azure.workload.identity/use`
+
+For annotations, maintenance jobs include:
+- Only [third-party annotations][5] from the Velero server deployment that are in the predefined list, currently including:
+  - `iam.amazonaws.com/role`
+
+These specific labels and annotations ensure proper integration with cloud provider identity systems.
 Maintenance jobs will not run for backup repositories whose backup storage location is set as readOnly.  
 
 [1]: velero-install.md#usage
 [2]: node-agent-concurrency.md
 [3]: backup-repository-configuration.md#full-maintenance-interval-customization
+[4]: https://github.com/vmware-tanzu/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L19-L21
+[5]: https://github.com/vmware-tanzu/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L23-L25

site/content/docs/v1.16/repository-maintenance.md

@@ -155,9 +155,22 @@ Status:
 - `Recent Maintenance` keeps the status of the recent 3 maintenance jobs, including its start time, result (succeeded/failed), completion time (if the maintenance job succeeded), or error message (if the maintenance failed)
 
 ### Others
-Maintenance jobs will inherit the labels, annotations, toleration, nodeSelector, service account, image, environment variables, cloud-credentials etc. from Velero deployment.  
+Maintenance jobs will inherit specific labels, annotations, toleration, nodeSelector, service account, image, environment variables, cloud-credentials etc. from Velero deployment.
+
+For labels, maintenance jobs include:
+- `velero.io/repo-name: <repository-name>` to identify which repository they are maintaining
+- Only [third-party labels][4] from the Velero server deployment that are in the predefined list, currently including:
+  - `azure.workload.identity/use`
+
+For annotations, maintenance jobs include:
+- Only [third-party annotations][5] from the Velero server deployment that are in the predefined list, currently including:
+  - `iam.amazonaws.com/role`
+
+These specific labels and annotations ensure proper integration with cloud provider identity systems.
 Maintenance jobs will not run for backup repositories whose backup storage location is set as readOnly.  
 
 [1]: velero-install.md#usage
 [2]: node-agent-concurrency.md
 [3]: backup-repository-configuration.md#full-maintenance-interval-customization
+[4]: https://github.com/vmware-tanzu/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L19-L21
+[5]: https://github.com/vmware-tanzu/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L23-L25