infra
/
kubernetes
1
0
Fork 0
Code Pull Requests 4 Activity

Compare commits

base: infra:ab38df1d9f79a6635984a5a05cf738307b6480b7
Branches Tags
infra:updatebot/authelia
infra:updatebot/paperless-ngx
infra:updatebot/firefly-iii
infra:updatebot/home-assistant
infra:master
infra:jenkins-buildroot
infra:xactmon-doc
infra:etcd
infra:dch-webhooks-secrets
...
compare: infra:4c1992b3c9b99fc4ce95fb94c053aae7bbfbe100
Branches Tags
infra:updatebot/authelia
infra:updatebot/paperless-ngx
infra:updatebot/firefly-iii
infra:updatebot/home-assistant
infra:master
infra:jenkins-buildroot
infra:xactmon-doc
infra:etcd
infra:dch-webhooks-secrets

3 Commits
ab38df1d9f ... 4c1992b3c9

Author SHA1 Message Date
Dustin 4c1992b3c9 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.
 2025-09-07 10:49:22 -05:00
Dustin 25d34efb4c v-m/alertmanager: Bring up replicas in parallel 
If something prevents the first AlertManager instance from starting, we
don't want to wait forever for it before starting the second.  That
pretty much defeats the purpose of having two instances.  Fortunately,
we can configure Kubernetes to bring up both instances simultaneously by
setting the pod management policyo to `Parallel`.
 2025-09-07 10:42:50 -05:00
Dustin e605e3d1ea v-m/alertmanager: Migrate PVC to Synology 
We also don't need a 4 GB volume for AlertManager; even 500 MB is
way too big for the tiny amount of data it stores, but that's about the
smallest size a filesystem can be.
 2025-09-07 10:42:13 -05:00
3 changed files with 13 additions and 1 deletions
Show Stats Expand all files Collapse all files

3
victoria-metrics/alertmanager.yaml
View File

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

10
victoria-metrics/kustomization.yaml
View File

@ -216,6 +216,16 @@ patches:
- --cluster.peer=alertmanager-0.alertmanager:9094 - --cluster.peer=alertmanager-0.alertmanager:9094
- --cluster.peer=alertmanager-1.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: | - patch: |
- op: add - op: add
path: /spec/volumeClaimTemplates/0/spec/storageClassName path: /spec/volumeClaimTemplates/0/spec/storageClassName

1
victoria-metrics/vmagent.yaml
View File

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