Skip to content

Commit 725417d

Browse files
authored
Merge pull request #3564 from ie-pham/tempogen
[tempo] rename overrides section
2 parents 7dafadd + 3800139 commit 725417d

File tree

5 files changed

+39
-12
lines changed

5 files changed

+39
-12
lines changed

charts/tempo/Chart.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ apiVersion: v2
22
name: tempo
33
description: Grafana Tempo Single Binary Mode
44
type: application
5-
version: 1.18.3
5+
version: 1.19.0
66
appVersion: 2.7.1
77
engine: gotpl
88
home: https://grafana.net

charts/tempo/README.md

+12-3
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# tempo
22

3-
![Version: 1.18.3](https://img.shields.io/badge/Version-1.18.3-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 2.7.1](https://img.shields.io/badge/AppVersion-2.7.1-informational?style=flat-square)
3+
![Version: 1.19.0](https://img.shields.io/badge/Version-1.19.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 2.7.1](https://img.shields.io/badge/AppVersion-2.7.1-informational?style=flat-square)
44

55
Grafana Tempo Single Binary Mode
66

@@ -61,7 +61,6 @@ Grafana Tempo Single Binary Mode
6161
| tempo.extraEnv | list | `[]` | Environment variables to add |
6262
| tempo.extraEnvFrom | list | `[]` | Environment variables from secrets or configmaps to add to the ingester pods |
6363
| tempo.extraVolumeMounts | list | `[]` | Volume mounts to add |
64-
| tempo.global_overrides.per_tenant_override_config | string | `"/conf/overrides.yaml"` | |
6564
| tempo.ingester | object | `{}` | Configuration options for the ingester. Refers to: https://grafana.com/docs/tempo/latest/configuration/#ingester |
6665
| tempo.livenessProbe.failureThreshold | int | `3` | |
6766
| tempo.livenessProbe.httpGet.path | string | `"/ready"` | |
@@ -74,7 +73,10 @@ Grafana Tempo Single Binary Mode
7473
| tempo.metricsGenerator.enabled | bool | `false` | If true, enables Tempo's metrics generator (https://grafana.com/docs/tempo/next/metrics-generator/) |
7574
| tempo.metricsGenerator.remoteWriteUrl | string | `"http://prometheus.monitoring:9090/api/v1/write"` | |
7675
| tempo.multitenancyEnabled | bool | `false` | |
77-
| tempo.overrides | object | `{}` | |
76+
| tempo.overrides | object | `{"defaults":{},"per_tenant_override_config":"/conf/overrides.yaml"}` | The standard overrides configuration section. This can include a `defaults` object for applying to all tenants (not to be confused with the `global` property of the same name, which overrides `max_byte_per_trace` for all tenants). For an example on how to enable the metrics generator using the `overrides` object, see the 'Activate metrics generator' section below. Refer to [Standard overrides](https://grafana.com/docs/tempo/latest/configuration/#standard-overrides) for more details. |
77+
| tempo.overrides.defaults | object | `{}` | Default config values for all tenants, can be overridden by per-tenant overrides. If a tenant's specific overrides are not found in the `per_tenant_overrides` block, the values in this `default` block will be used. Configs inside this block should follow the new overrides indentation format |
78+
| tempo.overrides.per_tenant_override_config | string | `"/conf/overrides.yaml"` | Path to the per tenant override config file. The values of the `per_tenant_overrides` config below will be written to the default path `/conf/overrides.yaml`. Users can set tenant-specific overrides settings in a separate file and point per_tenant_override_config to it if not using the per_tenant_overrides block below. |
79+
| tempo.per_tenant_overrides | object | `{}` | The `per tenant` aka `tenant-specific` runtime overrides. This allows overriding values set in the configuration on a per-tenant basis. Note that *all* values must be given for each per-tenant configuration block. Refer to [Runtime overrides](https://grafana.com/docs/tempo/latest/configuration/#runtime-overrides) and [Tenant-Specific overrides](https://grafana.com/docs/tempo/latest/configuration/#tenant-specific-overrides) documentation for more details. |
7880
| tempo.pullPolicy | string | `"IfNotPresent"` | |
7981
| tempo.querier | object | `{}` | Configuration options for the querier. Refers to: https://grafana.com/docs/tempo/latest/configuration/#querier |
8082
| tempo.queryFrontend | object | `{}` | Configuration options for the query-fronted. Refers to: https://grafana.com/docs/tempo/latest/configuration/#query-frontend |
@@ -153,6 +155,13 @@ The command removes all the Kubernetes components associated with the chart and
153155

154156
A major chart version change indicates that there is an incompatible breaking change needing manual actions.
155157

158+
### From Chart versions < 1.19.0
159+
* Breaking Change *
160+
In order to reduce confusion, the overrides configurations have been renamed as below.
161+
162+
`global_overrides` => `overrides` (this is where the defaults for every tenant is set)
163+
`overrides` => `per_tenant_overrides` (this is where configurations for specific tenants can be set)
164+
156165
### From Chart versions < 1.17.0
157166

158167
Please be aware that we've updated the Tempo version to 2.7, which includes some breaking changes

charts/tempo/README.md.gotmpl

+7
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,13 @@ The command removes all the Kubernetes components associated with the chart and
4040

4141
A major chart version change indicates that there is an incompatible breaking change needing manual actions.
4242

43+
### From Chart versions < 1.19.0
44+
* Breaking Change *
45+
In order to reduce confusion, the overrides configurations have been renamed as below.
46+
47+
`global_overrides` => `overrides` (this is where the defaults for every tenant is set)
48+
`overrides` => `per_tenant_overrides` (this is where configurations for specific tenants can be set)
49+
4350
### From Chart versions < 1.17.0
4451

4552
Please be aware that we've updated the Tempo version to 2.7, which includes some breaking changes

charts/tempo/templates/configmap-tempo.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,6 @@ metadata:
88
data:
99
overrides.yaml: |
1010
overrides:
11-
{{- toYaml .Values.tempo.overrides | nindent 6 }}
11+
{{- toYaml .Values.tempo.per_tenant_overrides | nindent 6 }}
1212
tempo.yaml: |
1313
{{- tpl .Values.config . | nindent 4 }}

charts/tempo/values.yaml

+18-7
Original file line numberDiff line numberDiff line change
@@ -65,10 +65,24 @@ tempo:
6565
# search:
6666
# concurrent_jobs: 2000
6767
retention: 24h
68-
# Global overrides
69-
global_overrides:
68+
# -- The standard overrides configuration section. This can include a `defaults` object for applying to all tenants (not to be confused with the `global` property of the same name, which overrides `max_byte_per_trace` for all tenants). For an example on how to enable the metrics generator using the `overrides` object, see the 'Activate metrics generator' section below. Refer to [Standard overrides](https://grafana.com/docs/tempo/latest/configuration/#standard-overrides) for more details.
69+
overrides:
70+
# -- Default config values for all tenants, can be overridden by per-tenant overrides. If a tenant's specific overrides are not found in the `per_tenant_overrides` block, the values in this `default` block will be used. Configs inside this block should follow the new overrides indentation format
71+
defaults: {}
72+
# metrics_generator:
73+
# processors:
74+
# - service-graphs
75+
# - span-metrics
76+
77+
# -- Path to the per tenant override config file. The values of the `per_tenant_overrides` config below will be written to the default path `/conf/overrides.yaml`. Users can set tenant-specific overrides settings in a separate file and point per_tenant_override_config to it if not using the per_tenant_overrides block below.
7078
per_tenant_override_config: /conf/overrides.yaml
71-
overrides: {}
79+
# -- The `per tenant` aka `tenant-specific` runtime overrides. This allows overriding values set in the configuration on a per-tenant basis. Note that *all* values must be given for each per-tenant configuration block. Refer to [Runtime overrides](https://grafana.com/docs/tempo/latest/configuration/#runtime-overrides) and [Tenant-Specific overrides](https://grafana.com/docs/tempo/latest/configuration/#tenant-specific-overrides) documentation for more details.
80+
per_tenant_overrides: {}
81+
# 'tenant-id':
82+
# metrics_generator:
83+
# processors:
84+
# - service-graphs
85+
# - span-metrics
7286

7387
# Tempo server configuration.
7488
# Refers to: https://grafana.com/docs/tempo/latest/configuration/#server
@@ -177,11 +191,8 @@ config: |
177191
query_frontend:
178192
{{- toYaml .Values.tempo.queryFrontend | nindent 6 }}
179193
overrides:
180-
{{- toYaml .Values.tempo.global_overrides | nindent 6 }}
194+
{{- toYaml .Values.tempo.overrides | nindent 6 }}
181195
{{- if .Values.tempo.metricsGenerator.enabled }}
182-
metrics_generator_processors:
183-
- 'service-graphs'
184-
- 'span-metrics'
185196
metrics_generator:
186197
storage:
187198
path: "/tmp/tempo"

0 commit comments

Comments
 (0)