v-m/vmagent: Start in parallel

As with AlertManager, the point of having multiple replicas of `vmagent`
is so that one is always running, even if the other fails.  Thus, we
want to start the pods in parallel so that if the first one does not
come up, the second one at least has a chance.

victoria-metrics/alertmanager.yaml

@@ -70,6 +70,7 @@ spec:
       - name: config
         configMap:
           name: alertmanager
+  podManagementPolicy: Parallel
   volumeClaimTemplates:
   - apiVersion: v1
     kind: PersistentVolumeClaim
@@ -83,4 +84,4 @@ spec:
       - ReadWriteOnce
       resources:
         requests:
-          storage: 4G
+          storage: 500M

victoria-metrics/kustomization.yaml

@@ -216,6 +216,16 @@ patches:
             - --cluster.peer=alertmanager-0.alertmanager:9094
             - --cluster.peer=alertmanager-1.alertmanager:9094
 
+- patch: |
+    - op: add
+      path: /spec/volumeClaimTemplates/0/spec/storageClassName
+      value: synology-iscsi
+  target:
+    group: apps
+    version: v1
+    kind: StatefulSet
+    name: alertmanager
+
 - patch: |
     - op: add
       path: /spec/volumeClaimTemplates/0/spec/storageClassName

victoria-metrics/vmagent.yaml

@@ -138,3 +138,4 @@ spec:
           name: vmagent
       - name: tmpdata
         emptyDir: {}
+  podManagementPolicy: Parallel