[velero] Have separate resource usages for velero server pod and upgradeCRDs job pod

charts/velero/Chart.yaml

@@ -3,7 +3,7 @@ appVersion: 1.12.1
 kubeVersion: ">=1.16.0-0"
 description: A Helm chart for velero
 name: velero
-version: 5.1.2
+version: 5.1.3
 home: https://github.com/vmware-tanzu/velero
 icon: https://cdn-images-1.medium.com/max/1600/1*-9mb3AKnKdcL_QD3CMnthQ.png
 sources:

charts/velero/templates/deployment.yaml

@@ -155,7 +155,7 @@ spec:
             - --namespace={{ . }}
             {{- end }}
           {{- end }}
-          {{- with .Values.resources }}
+          {{- with .Values.resources.server }}
           resources:
             {{- toYaml . | nindent 12 }}
           {{- end }}

charts/velero/templates/upgrade-crds/upgrade-crds.yaml

@@ -75,7 +75,7 @@ spec:
           args:
             - -c
             - /velero install --crds-only --dry-run -o yaml | /tmp/kubectl apply -f -
-          {{- with .Values.resources }}
+          {{- with .Values.resources.upgradeJob }}
           resources:
             {{- toYaml . | nindent 12 }}
           {{- end }}

charts/velero/values.yaml

@@ -71,15 +71,25 @@ podLabels: {}
 # Number of old history to retain to allow rollback (If not set, default Kubernetes value is set to 10)
 # revisionHistoryLimit: 1
 
-# Resource requests/limits to specify for the Velero deployment.
+# Resource requests/limits to specify for the Velero deployment and the upgrade CRDs job.
 # https://velero.io/docs/v1.6/customize-installation/#customize-resource-requests-and-limits
 resources:
-  requests:
-    cpu: 500m
-    memory: 128Mi
-  limits:
-    cpu: 1000m
-    memory: 512Mi
+# Resource requests for the Velero deployment
+  server:
+    requests:
+      cpu: 500m
+      memory: 128Mi
+    limits:
+      cpu: 1000m
+      memory: 512Mi
+# Resource requests for the upgrade CRDs job
+  upgradeJob:
+    requests:
+      cpu: 50m
+      memory: 64Mi
+    limits:
+      cpu: 100m
+      memory: 128Mi
 
 # Configure the dnsPolicy of the Velero deployment
 # See: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-s-dns-policy