DirectorySecurity AdvisoriesPricing
Sign in
Directory
telegraf logoHELM

telegraf

Helm chart
Last changed
Request a free trial

Contact our team to test out this Helm chart and related images for free. Please also indicate any other images you would like to evaluate.

Overview
Chart versions
Default values
Chart metadata
Images

Tag:
Compare:

1
## Default values.yaml for Telegraf
2
## This is a YAML-formatted file.
3
## ref: https://hub.docker.com/r/library/telegraf/tags/
4
5
replicaCount: 1
6
image:
7
repo: cgr.dev/scratch-images/test-tmp/telegraf
8
tag: 1.39.3-r7@sha256:ffb707aedd9e0b84d264dd088b28aa2f3e93dbf0903ec5d1e5c573ff6b44dc1b
9
pullPolicy: IfNotPresent
10
## Annotations to add to the Deployment object itself.
11
## Use podAnnotations below to annotate the pods.
12
deploymentAnnotations: {}
13
podAnnotations: {}
14
podLabels: {}
15
imagePullSecrets: []
16
## Configure args passed to Telegraf containers
17
args: []
18
# The name of a secret in the same kubernetes namespace which contains values to
19
# be added to the environment (must be manually created)
20
# This can be useful for auth tokens, etc.
21
22
## Init containers to run before Telegraf starts
23
## Useful for waiting on dependencies, preparing configs, or setting permissions
24
## Example:
25
# initContainers:
26
# - name: wait-for-service
27
# image: busybox:1.36
28
# command: ['sh', '-c', 'until nc -z myservice 8086; do sleep 1; done']
29
initContainers: []
30
# envFromSecret: "telegraf-tokens"
31
env:
32
- name: HOSTNAME
33
value: "telegraf-polling-service"
34
# An older "volumeMounts" key was previously added which will likely
35
# NOT WORK as you expect. Please use this newer configuration.
36
37
# volumes:
38
# - name: telegraf-output-influxdb2
39
# configMap:
40
# name: "telegraf-output-influxdb2"
41
# mountPoints:
42
# - name: telegraf-output-influxdb2
43
# mountPath: /etc/telegraf/conf.d
44
# subPath: influxdb2.conf
45
46
## Configure resource requests and limits
47
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
48
resources: {}
49
# requests:
50
# memory: 128Mi
51
# cpu: 100m
52
# limits:
53
# memory: 128Mi
54
# cpu: 100m
55
56
## Node labels for pod assignment
57
## ref: https://kubernetes.io/docs/user-guide/node-selection/
58
nodeSelector: {}
59
## Affinity for pod assignment
60
## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
61
##
62
affinity: {}
63
## Tolerations for pod assignment
64
## Ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
65
##
66
tolerations: []
67
# - key: "key"
68
# operator: "Equal|Exists"
69
# value: "value"
70
# effect: "NoSchedule|PreferNoSchedule|NoExecute(1.6 only)"
71
72
## Configure the updateStrategy used to replace Telegraf Pods
73
## See https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/deployment-v1/
74
updateStrategy: {}
75
# type: RollingUpdate|Recreate
76
# rollingUpdate:
77
# maxUnavailable: 1
78
# maxSurge: 1
79
80
service:
81
enabled: true
82
type: ClusterIP
83
annotations: {}
84
rbac:
85
# Specifies whether RBAC resources should be created
86
create: true
87
# Create only for the release namespace or cluster wide (Role vs ClusterRole)
88
clusterWide: false
89
# Rules for the created rule
90
rules: []
91
# When using the prometheus input to scrape all pods you need extra rules set to the ClusterRole to be
92
# able to scan the pods for scraping labels. The following rules have been taken from:
93
# https://github.com/helm/charts/blob/master/stable/prometheus/templates/server-clusterrole.yaml#L8-L46
94
# - apiGroups:
95
# - ""
96
# resources:
97
# - nodes
98
# - nodes/proxy
99
# - nodes/metrics
100
# - services
101
# - endpoints
102
# - pods
103
# - ingresses
104
# - configmaps
105
# verbs:
106
# - get
107
# - list
108
# - watch
109
# - apiGroups:
110
# - "extensions"
111
# resources:
112
# - ingresses/status
113
# - ingresses
114
# verbs:
115
# - get
116
# - list
117
# - watch
118
# - nonResourceURLs:
119
# - "/metrics"
120
# verbs:
121
# - get
122
123
serviceAccount:
124
# Specifies whether a ServiceAccount should be created
125
create: true
126
# The name of the ServiceAccount to use.
127
# If not set and create is true, a name is generated using the fullname template
128
name:
129
# Annotations for the ServiceAccount
130
annotations: {}
131
## Specify priorityClassName
132
## Ref: https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/
133
# priorityClassName: system-node-critical
134
135
## Exposed telegraf configuration
136
## For full list of possible values see `/docs/all-config-values.yaml` and `/docs/all-config-values.toml`
137
## ref: https://docs.influxdata.com/telegraf/v1.1/administration/configuration/
138
config:
139
agent:
140
interval: "10s"
141
round_interval: true
142
metric_batch_size: 1000
143
metric_buffer_limit: 10000
144
collection_jitter: "0s"
145
flush_interval: "10s"
146
flush_jitter: "0s"
147
precision: ""
148
debug: false
149
quiet: false
150
logfile: ""
151
hostname: "$HOSTNAME"
152
omit_hostname: false
153
processors:
154
- enum:
155
mapping:
156
field: "status"
157
dest: "status_code"
158
value_mappings:
159
healthy: 1
160
problem: 2
161
critical: 3
162
outputs:
163
- influxdb:
164
urls:
165
- "http://influxdb.monitoring.svc:8086"
166
database: "telegraf"
167
inputs:
168
- statsd:
169
service_address: ":8125"
170
percentiles:
171
- 50
172
- 95
173
- 99
174
metric_separator: "_"
175
allowed_pending_messages: 10000
176
percentile_limit: 1000
177
metrics:
178
health:
179
enabled: false
180
service_address: "http://:8888"
181
threshold: 5000.0
182
internal:
183
enabled: true
184
collect_memstats: false
185
# Lifecycle hooks
186
# hooks:
187
# postStart: ["/bin/sh", "-c", "echo Telegraf started"]
188
# preStop: ["/bin/sh", "-c", "sleep 60"]
189
190
## Pod disruption budget configuration
191
##
192
pdb:
193
## Specifies whether a Pod disruption budget should be created
194
##
195
create: true
196
minAvailable: 1
197
# maxUnavailable: 1
198
# containerPorts:
199
# - name: http
200
# containerPort: 9273
201
# protocol: TCP
202

The trusted source for open source

Talk to an expert
PrivacyTerms

Product

Chainguard ContainersChainguard LibrariesChainguard VMsChainguard OS PackagesChainguard ActionsChainguard Agent SkillsIntegrationsPricing
© 2026 Chainguard, Inc. All Rights Reserved.
Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.