forked from jitsi-contrib/jitsi-helm
-
Notifications
You must be signed in to change notification settings - Fork 0
/
values.yaml
488 lines (422 loc) · 11.6 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
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
# Default values for jitsi-meet.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
global:
# Set your cluster's DNS domain here.
# "cluster.local" should work for most environments.
# Set to "" to disable the use of FQDNs (default in older chart versions).
clusterDomain: cluster.local
podLabels: {}
podAnnotations: {}
releaseSecretsOverride:
enabled: false
#Support environment variables from pre-created secrets, such as 1Password operator
#extraEnvFrom:
# - secretRef:
# name: '{{ include "prosody.fullname" . }}-overrides'
# optional: true
imagePullSecrets: []
nameOverride: ""
fullnameOverride: ""
enableAuth: false
enableGuests: true
# Where Jitsi Web UI is made available
# such as jitsi.example.com
publicURL: ""
tz: Europe/Amsterdam
image:
pullPolicy: IfNotPresent
## WebSocket configuration:
#
# Both Colibri and XMPP WebSockets are disabled by default,
# since some LoadBalancer / Reverse Proxy setups can't pass
# WebSocket connections properly, which might result in breakage
# for some clients.
#
# Enable both Colibri and XMPP WebSockets to replicate the current
# upstream `meet.jit.si` setup. Keep both disabled to replicate
# older setups which might be more compatible in some cases.
websockets:
## Colibri (JVB signalling):
colibri:
enabled: false
## XMPP (Prosody signalling):
xmpp:
enabled: false
web:
replicaCount: 1
image:
repository: jitsi/web
custom:
contInit:
_10_config: ""
defaults:
_default: ""
_ffdhe2048_txt: ""
_interface_config_js: ""
_meet_conf: ""
_nginx_conf: ""
_settings_config_js: ""
_ssl_conf: ""
_system_config_js: ""
extraEnvs: {}
service:
type: ClusterIP
port: 80
## If you want to expose the Jitsi Web service directly
# (bypassing the Ingress Controller), use this:
#
# type: NodePort
# nodePort: 30580
# port: 80
externalIPs: []
ingress:
enabled: false
# ingressClassName: "nginx-ingress-0"
annotations: {}
# kubernetes.io/tls-acme: "true"
hosts:
- host: jitsi.local
paths: ['/']
tls: []
# - secretName: jitsi-web-certificate
# hosts:
# - jitsi.local
# Useful for ingresses that don't support http-to-https redirect by themself, (namely: GKE),
httpRedirect: false
# When tls-termination by the ingress is not wanted, enable this and set web.service.type=Loadbalancer
httpsEnabled: false
## Resolver IP for nginx.
#
# Starting with version `stable-8044`, the web container can
# auto-detect the nameserver from /etc/resolv.conf.
# Use this option if you want to override the nameserver IP.
#
# resolverIP: 10.43.0.10
livenessProbe:
httpGet:
path: /
port: 80
readinessProbe:
httpGet:
path: /
port: 80
podLabels: {}
podAnnotations: {}
podSecurityContext: {}
# fsGroup: 2000
securityContext: {}
# capabilities:
# drop:
# - ALL
# readOnlyRootFilesystem: true
# runAsNonRoot: true
# runAsUser: 1000
resources: {}
# We usually recommend not to specify default resources and to leave this as a conscious
# choice for the user. This also increases chances charts run on environments with little
# resources, such as Minikube. If you do want to specify resources, uncomment the following
# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
# limits:
# cpu: 100m
# memory: 128Mi
# requests:
# cpu: 100m
# memory: 128Mi
nodeSelector: {}
tolerations: []
affinity: {}
jicofo:
replicaCount: 1
image:
repository: jitsi/jicofo
custom:
contInit:
_10_config: ""
defaults:
_jicofo_conf: ""
_logging_properties: ""
xmpp:
password:
componentSecret:
livenessProbe:
tcpSocket:
port: 8888
readinessProbe:
tcpSocket:
port: 8888
podLabels: {}
podAnnotations: {}
podSecurityContext: {}
securityContext: {}
resources: {}
nodeSelector: {}
tolerations: []
affinity: {}
extraEnvs: {}
jvb:
replicaCount: 1
image:
repository: jitsi/jvb
xmpp:
user: jvb
password:
## Set public IP addresses to be advertised by JVB.
# You can specify your nodes' IP addresses,
# or IP addresses of proxies/LoadBalancers used for your
# Jitsi Meet installation. Or both!
#
# Note that only the first IP address will be used for legacy
# `DOCKER_HOST_ADDRESS` environment variable.
#
# publicIPs:
# - 1.2.3.4
# - 5.6.7.8
## Use a STUN server to help some users punch through some
# especially nasty NAT setups. Usually makes sense for P2P calls.
stunServers: 'meet-jit-si-turnrelay.jitsi.net:443'
## Try to use the hostPort feature:
# (might not be supported by some clouds or CNI engines)
useHostPort: false
## Use host's network namespace:
# (not recommended, but might help for some cases)
useHostNetwork: false
## UDP transport port:
UDPPort: 10000
## Use a pre-defined external port for NodePort or LoadBalancer service,
# if needed. Will allocate a random port from allowed range if unset.
# (Default NodePort range for K8s is 30000-32767)
# nodePort: 10000
service:
enabled:
type: ClusterIP
externalTrafficPolicy: Cluster
externalIPs: []
## Annotations to be added to the service (if LoadBalancer is used)
##
annotations: {}
breweryMuc: jvbbrewery
livenessProbe:
httpGet:
path: /about/health
port: 8080
readinessProbe:
httpGet:
path: /about/health
port: 8080
podLabels: {}
podAnnotations: {}
podSecurityContext: {}
securityContext: {}
resources: {}
nodeSelector: {}
tolerations: []
affinity: {}
extraEnvs: {}
metrics:
enabled: false
image:
repository: docker.io/systemli/prometheus-jitsi-meet-exporter
tag: 1.2.3
pullPolicy: IfNotPresent
resources:
requests:
cpu: 10m
memory: 16Mi
limits:
cpu: 20m
memory: 32Mi
prometheusAnnotations: false
serviceMonitor:
enabled: true
selector:
release: prometheus-operator
interval: 10s
# honorLabels: false
grafanaDashboards:
enabled: false
labels:
grafana_dashboard: "1"
annotations: {}
octo:
enabled: false
jigasi:
## Enabling Jigasi will allow regular SIP clients to join Jitsi meetings
## or nearly real-time transcription.
enabled: false
## Use external Jigasi installation.
## This setting skips the creation of Jigasi Deployment altogether,
## instead creating just the config secret and enabling services.
## Defaults to disabled (use bundled Jigasi).
useExternalJigasi: false
replicaCount: 1
image:
repository: jitsi/jigasi
breweryMuc: jigasibrewery
## jigasi XMPP user credentials:
xmpp:
user: jigasi
password:
livenessProbe:
tcpSocket:
port: 8788
readinessProbe:
tcpSocket:
port: 8788
podLabels: {}
podAnnotations: {}
podSecurityContext: {}
securityContext: {}
resources: {}
nodeSelector: {}
tolerations: []
affinity: {}
extraEnvs: {}
jibri:
## Enabling Jibri will allow users to record
## and/or stream their meetings (e.g. to YouTube).
enabled: false
## Use external Jibri installation.
## This setting skips the creation of Jibri Deployment altogether,
## instead creating just the config secret
## and enabling recording/streaming services.
## Defaults to disabled (use bundled Jibri).
useExternalJibri: false
## Enable single-use mode for Jibri.
## With this setting enabled, every Jibri instance
## will become "expired" after being used once (successfully or not)
## and cleaned up (restarted) by Kubernetes.
##
## Note that detecting expired Jibri, restarting and registering it
## takes some time, so you'll have to make sure you have enough
## instances at your disposal.
## You might also want to make LivenessProbe fail faster.
singleUseMode: false
## Enable recording service.
## Set this to true/false to enable/disable local recordings.
## Defaults to enabled (allow local recordings).
recording: true
## Enable livestreaming service.
## Set this to true/false to enable/disable live streams.
## Defaults to disabled (livestreaming is forbidden).
livestreaming: false
## Enable multiple Jibri instances.
## If enabled (i.e. set to 2 or more), each Jibri instance
## will get an ID assigned to it, based on pod name.
## Multiple replicas are recommended for single-use mode.
replicaCount: 1
## Enable persistent storage for local recordings.
## If disabled, jibri pod will use a transient
## emptyDir-backed storage instead.
persistence:
enabled: false
size: 4Gi
## Set this to existing PVC name if you have one.
existingClaim:
storageClassName:
shm:
## Set to true to enable "/dev/shm" mount.
## May be required by built-in Chromium.
enabled: false
## If "true", will use host's shared memory dir,
## and if "false" — an emptyDir mount.
# useHost: false
# size: 256Mi
## Configure the update strategy for Jibri deployment.
## This may be useful depending on your persistence settings,
## e.g. when you use ReadWriteOnce PVCs.
## Default strategy is "RollingUpdate", which keeps
## the old instances up until the new ones are ready.
# strategy:
# type: RollingUpdate
image:
repository: jitsi/jibri
podLabels: {}
podAnnotations: {}
breweryMuc: jibribrewery
timeout: 90
## jibri XMPP user credentials:
xmpp:
user: jibri
password:
## recorder XMPP user credentials:
recorder:
user: recorder
password:
livenessProbe:
initialDelaySeconds: 5
periodSeconds: 5
failureThreshold: 2
exec:
command:
- /bin/bash
- "-c"
- >-
curl -sq localhost:2222/jibri/api/v1.0/health
| jq '"\(.status.health.healthStatus) \(.status.busyStatus)"'
| grep -qP 'HEALTHY (IDLE|BUSY)'
readinessProbe:
initialDelaySeconds: 5
periodSeconds: 5
failureThreshold: 2
exec:
command:
- /bin/bash
- "-c"
- >-
curl -sq localhost:2222/jibri/api/v1.0/health
| jq '"\(.status.health.healthStatus) \(.status.busyStatus)"'
| grep -qP 'HEALTHY (IDLE|BUSY)'
extraEnvs: {}
custom:
contInit:
_10_config: ""
defaults:
_autoscaler_sidecar_config: ""
_jibri_conf: ""
_logging_properties: ""
_xorg_video_dummy_conf: ""
serviceAccount:
# Specifies whether a service account should be created
create: true
# Annotations to add to the service account
annotations: {}
# The name of the service account to use.
# If not set and create is true, a name is generated using the fullname template
name:
xmpp:
domain: meet.jitsi
authDomain:
mucDomain:
internalMucDomain:
guestDomain:
extraCommonEnvs: {}
prosody:
enabled: true
useExternalProsody: false
server:
extraEnvFrom:
- secretRef:
name: '{{ include "prosody.fullname" . }}-jibri'
- secretRef:
name: '{{ include "prosody.fullname" . }}-jicofo'
- secretRef:
name: '{{ include "prosody.fullname" . }}-jigasi'
- secretRef:
name: '{{ include "prosody.fullname" . }}-jvb'
- configMapRef:
name: '{{ include "prosody.fullname" . }}-common'
image:
repository: jitsi/prosody
# service:
# ports:
# If Prosody c2s in needed on private net outside the cluster
# xmppc2snodePort: 30522
custom:
contInit:
_10_config: ""
defaults:
_prosody_cfg_lua: ""
_saslauthd_conf: ""
_jitsi_meet_cfg_lua: ""
tag: 'stable-9111'