Skip to content

Deploy Prometheus in high availability mode #416

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 13, 2022
Merged

Deploy Prometheus in high availability mode #416

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion chart/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,8 @@ promscale:
openTelemetry:
enabled: &otelEnabled true
# to pass extra args
extraArgs: []
extraArgs:
- "--metrics.high-availability=true"

extraEnv:
- name: "TOBS_TELEMETRY_INSTALLED_BY"
Expand Down Expand Up @@ -133,6 +134,11 @@ kube-prometheus-stack:
evaluationInterval: "1m"
# Prometheus metric retention
retention: 1d
# Number of replicas of each shard to deploy for a Prometheus deployment.
replicas: 2
replicaExternalLabelName: "__replica__"
# Promscale requires a cluster label to be present for high availability mode.
prometheusExternalLabelName: "cluster"
# The remote_read spec configuration for Prometheus.
# ref: https://github.com/prometheus-operator/prometheus-operator/blob/master/Documentation/api.md#remotereadspec
remoteRead:
Expand Down