forked from cetic/helm-zabbix
-
Notifications
You must be signed in to change notification settings - Fork 0
/
values.yaml
240 lines (227 loc) · 8.38 KB
/
values.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
# Default values for zabbix.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
# **Zabbix server** configurations
zabbixServer:
# -- Number of replicas of ``zabbixServer`` module
replicaCount: 1
# zabbixServer.hostPort -- optional set true open a port direct on node where zabbix server runs
hostPort: false
# zabbixServer.hostIP -- optional set hostIP different from 0.0.0.0 to open port only on this IP
hostIP: 0.0.0.0
resources: {}
image:
# -- Zabbix server Docker image name
repository: zabbix/zabbix-server-pgsql
# -- Tag of Docker image of Zabbix server
tag: ubuntu-5.4.1
# -- Pull policy of Docker image
pullPolicy: IfNotPresent
# -- List of dockerconfig secrets names to use when pulling images
pullSecrets: []
# -- Address of database host
DB_SERVER_HOST: "zabbix-postgresql"
# -- User of database
POSTGRES_USER: "zabbix"
# -- Password of database
POSTGRES_PASSWORD: "zabbix_pwd"
# -- Name of database
POSTGRES_DB: "zabbix"
service:
# -- Type of service in Kubernetes cluster
type: ClusterIP
# -- Port of service in Kubernetes cluster
port: 10051
# **PostgreSQL** configurations
postgresql:
# -- Create a database using Postgresql
enabled: true
# -- User of database
postgresqlUsername: zabbix
# -- Password of database
postgresqlPassword: zabbix_pwd
# -- Name of database
postgresqlDatabase: zabbix
# -- Password of``postgres`` user in Postgresql
postgresqlPostgresPassword: zabbix_pwd
# **Zabbix proxy** not functional for the moment, work is still in progress.
zabbixproxy:
# -- Enables use of **Zabbix proxy**
enabled: false
resources: {}
image:
# -- Zabbix proxy Docker image name
repository: zabbix/zabbix-proxy-mysql
# -- Tag of Docker image of Zabbix proxy
tag: ubuntu-5.4.1
# -- Pull policy of Docker image
pullPolicy: IfNotPresent
# -- List of dockerconfig secrets names to use when pulling images
pullSecrets: []
# -- The variable allows to switch Zabbix proxy mode. Bu default, value is 0 - active proxy. Allowed values are 0 and 1.
ZBX_PROXYMODE: 0
# -- Zabbix proxy hostname
# Case sensitive hostname
ZBX_HOSTNAME: zabbix-proxy # This variable is unique, case sensitive hostname.
# -- Zabbix server host
ZBX_SERVER_HOST: zabbix-server
# -- Zabbix server port
ZBX_SERVER_PORT: 10051
# -- Port of database
DB_SERVER_PORT: 3306
# -- Address of database host
DB_SERVER_HOST: maria-mariadb
# -- User of database
MYSQL_USER: admin
# Provide the path to a file which contains the user instead of using the variable MYSQL_USER
# MYSQL_USER_FILE: /run/secrets/MYSQL_USER
# zabbixproxy.MYSQL_PASSWORD -- Password of database
MYSQL_PASSWORD: password1
# Provide the path to a file which contains the passwoord instead of using the variable MYSQL_PASSWORD
# MYSQL_PASSWORD_FILE: /var/run/secrets/MYSQL_PASSWORD
# zabbixproxy.MYSQL_DATABASE -- default to zabbix ( to be precised later)
MYSQL_DATABASE: my_database
# ZBX_LOADMODULE: dummy1.so,dummy2.so # The variable is list of comma separated loadable Zabbix modules. It works with volume /var/lib/zabbix/modules.
# The variable is used to specify debug level, from 0 to 5
# ZBX_DEBUGLEVEL: 4
# The variable is used to specify timeout for processing checks. By default, value is 4.
#ZBX_TIMEOUT: 4
# -- The variable enable communication with Zabbix Java Gateway to collect Java related checks. By default, value is false.
ZBX_JAVAGATEWAY_ENABLE: false
# -- Cache size
ZBX_VMWARECACHESIZE: 128M
service:
# -- Type of service for Zabbix proxy
type: ClusterIP
# -- Port to expose service
port: 10051
# -- Port of application pod
targetPort: 10051
# **Zabbix agent** configurations
zabbixagent:
# -- Enables use of Zabbix agent
enabled: true
resources: {}
image:
# -- Zabbix agent Docker image name
repository: zabbix/zabbix-agent
# -- Tag of Docker image of Zabbix agent
tag: ubuntu-5.4.1
# -- Pull policy of Docker image
pullPolicy: IfNotPresent
# -- List of dockerconfig secrets names to use when pulling images
pullSecrets: []
# -- Zabbix agent hostname
# Case sensitive hostname
ZBX_HOSTNAME: zabbix-agent
# -- Zabbix server host
ZBX_SERVER_HOST: 127.0.0.1
# -- Zabbix server port
ZBX_SERVER_PORT: 10051
# -- This variable is boolean (true or false) and enables or disables feature of passive checks. By default, value is true
ZBX_PASSIVE_ALLOW: true
# -- The variable is comma separated list of allowed Zabbix server or proxy hosts for connections to Zabbix agent container.
ZBX_PASSIVESERVERS: 127.0.0.1
# -- This variable is boolean (true or false) and enables or disables feature of active checks
ZBX_ACTIVE_ALLOW: true
# The variable is comma separated list of allowed Zabbix server or proxy hosts for connections to Zabbix agent container. You may specify port.
# ZBX_ACTIVESERVERS:
# The variable is list of comma separated loadable Zabbix modules. It works with volume /var/lib/zabbix/modules.
# ZBX_LOADMODULE: dummy1.so,dummy2.so
# The variable is used to specify debug level, from 0 to 5
#ZBX_DEBUGLEVEL: 3
# The variable is used to specify timeout for processing checks. By default, value is 4.
#ZBX_TIMEOUT: 4
# -- The variable enable communication with Zabbix Java Gateway to collect Java related checks. By default, value is false.
ZBX_JAVAGATEWAY_ENABLE: false
# -- Cache size
ZBX_VMWARECACHESIZE: 128M
service:
# -- Type of service for Zabbix agent
type: ClusterIP
# -- Port to expose service
port: 10050
# -- Port of application pod
targetPort: 10050
# **Zabbix web** configurations
zabbixweb:
# -- Enables use of Zabbix web
enabled: true
image:
# -- Zabbix web Docker image name
repository: zabbix/zabbix-web-apache-pgsql
# -- Tag of Docker image of Zabbix web
tag: ubuntu-5.4.1
# -- Pull policy of Docker image
pullPolicy: IfNotPresent
# zabbixweb.image.pullSecrets -- List of dockerconfig secrets names to use when pulling images
pullSecrets: []
# -- Zabbix server host
ZBX_SERVER_HOST: zabbix-server
# -- Zabbix server port
ZBX_SERVER_PORT: 10051
# -- Address of database host
DB_SERVER_HOST: zabbix-postgresql
# -- Port of database
DB_SERVER_PORT: 5432
# -- User of database
POSTGRES_USER: zabbix
# -- Password of database
POSTGRES_PASSWORD: zabbix_pwd
# -- Name of database
POSTGRES_DB: zabbix
service:
# -- Type of service for Zabbix web
# -- NodePort
type: ClusterIP
# -- Port to expose service
port: 80
# -- Port of application pod
targetPort: 8080
# Ingress configurations
ingress:
# -- Enables Ingress
enabled: false
# -- Ingress annotations
annotations: {}
# -- Ingress hosts
hosts:
- host:
paths: []
# -- Ingress TLS configuration
tls: []
# - secretName: chart-example-tls
# hosts:
# - chart-example.local
livenessProbe:
# -- Path of health check of application
path: /
# -- Number of seconds after the container has started before liveness
initialDelaySeconds: 30
# -- Specifies that the kubelet should perform a liveness probe every N seconds
periodSeconds: 10
# -- Number of seconds after which the probe times out
timeoutSeconds: 5
# -- When a probe fails, Kubernetes will try failureThreshold times before giving up. Giving up in case of liveness probe means restarting the container. In case of readiness probe the Pod will be marked Unready
failureThreshold: 6
# -- Minimum consecutive successes for the probe to be considered successful after having failed
successThreshold: 1
readinessProbe:
# -- Path of health check of application
path: /
# -- Number of seconds after the container has started before readiness
initialDelaySeconds: 5
# -- Specifies that the kubelet should perform a readiness probe every N seconds
periodSeconds: 10
# -- Number of seconds after which the probe times out
timeoutSeconds: 5
# -- When a probe fails, Kubernetes will try failureThreshold times before giving up. Giving up in case of liveness probe means restarting the container. In case of readiness probe the Pod will be marked Unready
failureThreshold: 6
# -- Minimum consecutive successes for the probe to be considered successful after having failed
successThreshold: 1
# -- nodeSelector configurations
nodeSelector: {}
# -- Tolerations configurations
tolerations: []
# -- Affinity configurations
affinity: {}