Skip to content

Commit

Permalink
Merge pull request #3868 from consideRatio/pr/tweak-grafana
Browse files Browse the repository at this point in the history
support chart, grafana: allow memory to peak to 2x requests and disable readinessProbe
  • Loading branch information
consideRatio authored Apr 3, 2024
2 parents 120e88d + 3fe8547 commit 4cc0551
Showing 1 changed file with 11 additions and 3 deletions.
14 changes: 11 additions & 3 deletions helm-charts/support/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -281,6 +281,12 @@ grafana:
# type Recreate is required since we attach a PVC that can only be used by
# mounted for writing by one pod at the time.
type: Recreate
readinessProbe:
# With one grafana pod replica, having a readiness probe fail is pointless.
# We ensure it won't fail before the livenessProbe that would restart the
# container.
failureThreshold: 1000
initialDelaySeconds: 1

rbac:
# namespaced makes us not get ClusterRole service accounts etc, and we do
Expand All @@ -297,8 +303,10 @@ grafana:
# prometheus and grafana.
#
# Grafana's memory use seems to increase over time but seems reasonable to
# stay below 200Mi for years to come. Grafana's CPU use seems minuscule with
# peaks at up to 9m CPU from one user is browsing its dashboards.
# stay below 200Mi in general. Memory can peak when dashboards are updated,
# and was increased to 400Mi as its been seen getting OOMKilled. Grafana's CPU
# use seems minuscule with peaks at up to 9m CPU from one user is browsing its
# dashboards.
#
# PromQL queries for CPU and memory use:
# - CPU: sum(rate(container_cpu_usage_seconds_total{container="grafana", namespace="support"}[5m])) by (pod)
Expand All @@ -307,7 +315,7 @@ grafana:
resources:
limits:
cpu: 100m
memory: 200Mi
memory: 400Mi
requests:
cpu: 10m
memory: 200Mi
Expand Down

0 comments on commit 4cc0551

Please sign in to comment.