Skip to content

Commit

Permalink
Add two prometheus replicas for high availability
Browse files Browse the repository at this point in the history
flightdeck-prometheus is used for autoscaling as well, so if this goes
down for whatever reason or whatever node, then it would cause the site
to suffer performance problems. We can mitigate this risk by having
multiple nodes.

This also means currently our federated instance is getting twice as
much data, since it's pulling from both replicas and not being
deduplicated yet.
  • Loading branch information
ayellapragada committed Nov 22, 2021
1 parent 3010fdd commit 4ed1916
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions common/workload-platform/flightdeck-prometheus.yaml
Original file line number Diff line number Diff line change
@@ -1,3 +1,13 @@
prometheus:
spec:
replicas: 2
topologySpreadConstraints:
- maxSkew: 1
topologyKey: "topology.kubernetes.io/zone"
whenUnsatisfiable: DoNotSchedule
labelSelector:
matchLabels:
prometheus: flightdeck-prometheus
podMonitors:
- name: envoy-stats-monitor
additionalLabels:
Expand Down

0 comments on commit 4ed1916

Please sign in to comment.