Skip to content

Commit

Permalink
Merge branch 'main' into pvc
Browse files Browse the repository at this point in the history
Signed-off-by: Martin Balint <[email protected]>
  • Loading branch information
martinbalint committed Nov 27, 2024
2 parents 9a973ca + 624f414 commit 48854f1
Show file tree
Hide file tree
Showing 10 changed files with 70 additions and 18 deletions.
4 changes: 2 additions & 2 deletions charts/grafana/Chart.yaml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
apiVersion: v2
name: grafana
version: 8.6.0
appVersion: 11.3.0
version: 8.6.3
appVersion: 11.3.1
kubeVersion: "^1.8.0-0"
description: The leading tool for querying and visualizing time series and metrics.
home: https://grafana.com
Expand Down
2 changes: 1 addition & 1 deletion charts/grafana/templates/deployment.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ spec:
template:
metadata:
labels:
{{- include "grafana.selectorLabels" . | nindent 8 }}
{{- include "grafana.labels" . | nindent 8 }}
{{- with .Values.podLabels }}
{{- toYaml . | nindent 8 }}
{{- end }}
Expand Down
2 changes: 1 addition & 1 deletion charts/grafana/templates/statefulset.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ spec:
template:
metadata:
labels:
{{- include "grafana.selectorLabels" . | nindent 8 }}
{{- include "grafana.labels" . | nindent 8 }}
{{- with .Values.podLabels }}
{{- toYaml . | nindent 8 }}
{{- end }}
Expand Down
29 changes: 28 additions & 1 deletion charts/grafana/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -673,9 +673,15 @@ datasources: {}
# - name: Prometheus

## Configure grafana alerting (can be templated)
## ref: http://docs.grafana.org/administration/provisioning/#alerting
## ref: https://docs.grafana.com/alerting/set-up/provision-alerting-resources/file-provisioning/
##
alerting: {}
# policies.yaml:
# apiVersion: 1
# policies:
# - orgId: 1
# receiver: first_uid
#
# rules.yaml:
# apiVersion: 1
# groups:
Expand Down Expand Up @@ -720,6 +726,7 @@ alerting: {}
# some_key: some_value
# labels:
# team: sre_team_1
#
# contactpoints.yaml:
# secret:
# apiVersion: 1
Expand All @@ -737,6 +744,26 @@ alerting: {}
# group: app-stack
# summary: |
# {{ `{{ include "default.message" . }}` }}
#
# templates.yaml:
# apiVersion: 1
# templates:
# - orgId: 1
# name: my_first_template
# template: |
# {{ `
# {{ define "my_first_template" }}
# Custom notification message
# {{ end }}
# ` }}
#
# mutetimes.yaml
# apiVersion: 1
# muteTimes:
# - orgId: 1
# name: mti_1
# # refer to https://prometheus.io/docs/alerting/latest/configuration/#time_interval-0
# time_intervals: {}

## Configure notifiers
## ref: http://docs.grafana.org/administration/provisioning/#alert-notification-channels
Expand Down
4 changes: 2 additions & 2 deletions charts/rollout-operator/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ apiVersion: v2
name: rollout-operator
description: "Grafana rollout-operator"
type: application
version: 0.19.1
appVersion: v0.19.1
version: 0.20.0
appVersion: v0.20.0
home: https://github.com/grafana/rollout-operator
kubeVersion: ^1.10.0-0
2 changes: 1 addition & 1 deletion charts/rollout-operator/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Helm chart for deploying [Grafana rollout-operator](https://github.com/grafana/r

# rollout-operator

![Version: 0.19.1](https://img.shields.io/badge/Version-0.19.1-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: v0.19.1](https://img.shields.io/badge/AppVersion-v0.19.1-informational?style=flat-square)
![Version: 0.20.0](https://img.shields.io/badge/Version-0.20.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: v0.20.0](https://img.shields.io/badge/AppVersion-v0.20.0-informational?style=flat-square)

Grafana rollout-operator

Expand Down
2 changes: 1 addition & 1 deletion charts/tempo-distributed/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ apiVersion: v2
name: tempo-distributed
description: Grafana Tempo in MicroService mode
type: application
version: 1.22.1
version: 1.23.2
appVersion: 2.6.0
engine: gotpl
home: https://grafana.com/docs/tempo/latest/
Expand Down
12 changes: 9 additions & 3 deletions charts/tempo-distributed/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# tempo-distributed

![Version: 1.22.1](https://img.shields.io/badge/Version-1.22.1-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 2.6.0](https://img.shields.io/badge/AppVersion-2.6.0-informational?style=flat-square)
![Version: 1.23.2](https://img.shields.io/badge/Version-1.23.1-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 2.6.0](https://img.shields.io/badge/AppVersion-2.6.0-informational?style=flat-square)

Grafana Tempo in MicroService mode

Expand Down Expand Up @@ -360,7 +360,7 @@ The memcached default args are removed and should be provided manually. The sett
| distributor.topologySpreadConstraints | string | Defaults to allow skew no more then 1 node per AZ | topologySpread for distributor pods. Passed through `tpl` and, thus, to be configured as string |
| enterprise.enabled | bool | `false` | |
| enterprise.image.repository | string | `"grafana/enterprise-traces"` | Grafana Enterprise Metrics container image repository. Note: for Grafana Tempo use the value 'image.repository' |
| enterprise.image.tag | string | `"v2.4.0"` | Grafana Enterprise Metrics container image tag. Note: for Grafana Tempo use the value 'image.tag' |
| enterprise.image.tag | string | `"v2.6.1"` | Grafana Enterprise Metrics container image tag. Note: for Grafana Tempo use the value 'image.tag' |
| enterpriseFederationFrontend.affinity | string | Hard node and soft zone anti-affinity | Affinity for federation-frontend pods. Passed through `tpl` and, thus, to be configured as string |
| enterpriseFederationFrontend.autoscaling.enabled | bool | `false` | Enable autoscaling for the federation-frontend |
| enterpriseFederationFrontend.autoscaling.maxReplicas | int | `3` | Maximum autoscaling replicas for the federation-frontend |
Expand Down Expand Up @@ -755,7 +755,13 @@ The memcached default args are removed and should be provided manually. The sett
| queryFrontend.autoscaling.targetMemoryUtilizationPercentage | string | `nil` | Target memory utilisation percentage for the query-frontend |
| queryFrontend.config.max_outstanding_per_tenant | int | `2000` | Maximum number of outstanding requests per tenant per frontend; requests beyond this error with HTTP 429. |
| queryFrontend.config.max_retries | int | `2` | Number of times to retry a request sent to a querier |
| queryFrontend.config.metrics.max_duration | string | `"3h"` | |
| queryFrontend.config.metrics.concurrent_jobs | int | `1000` | The number of concurrent jobs to execute when querying the backend. |
| queryFrontend.config.metrics.duration_slo | string | `"0s"` | If set to a non-zero value, it's value will be used to decide if query is within SLO or not. Query is within SLO if it returned 200 within duration_slo seconds OR processed throughput_slo bytes/s data. NOTE: `duration_slo` and `throughput_bytes_slo` both must be configured for it to work |
| queryFrontend.config.metrics.interval | string | `"5m"` | The target length of time for each job to handle when querying the backend. |
| queryFrontend.config.metrics.max_duration | string | `"3h"` | The maximum allowed time range for a metrics query. 0 disables this limit. |
| queryFrontend.config.metrics.query_backend_after | string | `"30m"` | query_backend_after controls where the query-frontend searches for traces. Time ranges older than query_backend_after will be searched in the backend/object storage only. Time ranges between query_backend_after and now will be queried from the metrics-generators. |
| queryFrontend.config.metrics.target_bytes_per_job | int | `104857600` | The target number of bytes for each job to handle when querying the backend. |
| queryFrontend.config.metrics.throughput_bytes_slo | int | `0` | If set to a non-zero value, it's value will be used to decide if query is within SLO or not. Query is within SLO if it returned 200 within duration_slo seconds OR processed throughput_slo bytes/s data. |
| queryFrontend.config.search.concurrent_jobs | int | `1000` | The number of concurrent jobs to execute when searching the backend |
| queryFrontend.config.search.target_bytes_per_job | int | `104857600` | The target number of bytes for each job to handle when performing a backend search |
| queryFrontend.config.trace_by_id | object | `{"query_shards":50}` | Trace by ID lookup configuration |
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -42,9 +42,6 @@ spec:
{{- with .Values.tempo.podLabels }}
{{- toYaml . | nindent 8 }}
{{- end }}
{{- with .Values.ingester.podLabels }}
{{- toYaml . | nindent 8 }}
{{- end }}
annotations:
checksum/config: {{ include (print $.Template.BasePath "/configmap-tempo.yaml") . | sha256sum }}
{{- with .Values.tempo.podAnnotations }}
Expand Down
28 changes: 25 additions & 3 deletions charts/tempo-distributed/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -844,9 +844,26 @@ queryFrontend:
# -- The number of shards to split a trace by id query into.
query_shards: 50
metrics:
# The maximum allowed time range for a metrics query.
# -- The number of concurrent jobs to execute when querying the backend.
concurrent_jobs: 1000
# -- The target number of bytes for each job to handle when querying the backend.
target_bytes_per_job: 104857600
# -- The maximum allowed time range for a metrics query.
# 0 disables this limit.
max_duration: 3h
# -- query_backend_after controls where the query-frontend searches for traces.
# Time ranges older than query_backend_after will be searched in the backend/object storage only.
# Time ranges between query_backend_after and now will be queried from the metrics-generators.
query_backend_after: 30m
# -- The target length of time for each job to handle when querying the backend.
interval: 5m
# -- If set to a non-zero value, it's value will be used to decide if query is within SLO or not.
# Query is within SLO if it returned 200 within duration_slo seconds OR processed throughput_slo bytes/s data.
# NOTE: `duration_slo` and `throughput_bytes_slo` both must be configured for it to work
duration_slo: 0s
# -- If set to a non-zero value, it's value will be used to decide if query is within SLO or not.
# Query is within SLO if it returned 200 within duration_slo seconds OR processed throughput_slo bytes/s data.
throughput_bytes_slo: 0
autoscaling:
# -- Enable autoscaling for the query-frontend
enabled: false
Expand Down Expand Up @@ -1366,8 +1383,13 @@ config: |
trace_by_id:
query_shards: {{ .Values.queryFrontend.config.trace_by_id.query_shards }}
metrics:
concurrent_jobs: {{ .Values.queryFrontend.config.metrics.concurrent_jobs }}
target_bytes_per_job: {{ .Values.queryFrontend.config.metrics.target_bytes_per_job }}
max_duration: {{ .Values.queryFrontend.config.metrics.max_duration }}
query_backend_after: {{ .Values.queryFrontend.config.metrics.query_backend_after }}
interval: {{ .Values.queryFrontend.config.metrics.interval }}
duration_slo: {{ .Values.queryFrontend.config.metrics.duration_slo }}
throughput_bytes_slo: {{ .Values.queryFrontend.config.metrics.throughput_bytes_slo }}
ingester:
lifecycler:
ring:
Expand Down Expand Up @@ -2049,7 +2071,7 @@ enterprise:
# -- Grafana Enterprise Metrics container image repository. Note: for Grafana Tempo use the value 'image.repository'
repository: grafana/enterprise-traces
# -- Grafana Enterprise Metrics container image tag. Note: for Grafana Tempo use the value 'image.tag'
tag: v2.4.0
tag: v2.6.1
# Note: pullPolicy and optional pullSecrets are set in toplevel 'image' section, not here

# In order to use Grafana Enterprise Traces features, you will need to provide the contents of your Grafana Enterprise Traces
Expand Down

0 comments on commit 48854f1

Please sign in to comment.