-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathvalues.yaml
5045 lines (4708 loc) · 153 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
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
## Global parameters
##
global:
## Global Docker image registry for Cognigy images
##
imageRegistry: ""
## If neither Cognigy MongoDB Helm Chart (https://github.com/Cognigy/cognigy-mongodb-helm-chart) nor MongoDB Atlas is used
## set "mongodb.enabled": false. It will skip user initialization tasks. However, you will need to create users/passwords manually
mongodb:
enabled: true
## MongoDB connection scheme, for Cognigy MongoDB Helm Chart use scheme: "mongodb", for MongoDB Atlas use scheme: "mongodb+srv"
scheme: "mongodb"
## Parameters for MongoDB connection, leave empty for Cognigy MongoDB Helm Chart
## For MongoDB Atlas set params: "?retryWrites=true&w=majority"
params: ""
## This MongoDB user and password must have the permission to create users and databases, so normally it is admin or root
## It does NOT have to be root user. We use these key names to be compatible with Bitnami MongoDB Helm Chert
auth:
rootUser: root
rootPassword: ""
## Optionally provide the name of an existing secret with MongoDB credentials. Mandatory keys: `username` and `password`, that contains the value
## of "rootUser" and "rootPassword"
## NOTE: When it's set the previous parameters "rootUser" and "rootPassword" are ignored.
##
existingSecret: ""
## MongoDB Atlas cluster parameters
atlas:
# Specify MongoDB Atlas projectId and clusterName
projectId: ""
clusterName: ""
# Specify publicAPIKey and privateAPIKey with "Project Owner" permissions for the Project in which MongoDB Cluster is located
## For more information refer to MongoDB Atlas documentation: https://www.mongodb.com/docs/atlas/configure-api-access/#grant-programmatic-access-to-service
publicAPIKey: ""
privateAPIKey: ""
## Optionally provide the name of an existing secret with MongoDB Atlas credentials. Mandatory keys: `projectid`, `clustername`, `apikeypublic` and `apikeyprivate`
## that contains the value of MongoDB Atlas projectId, clusterName, publicAPIKey and privateAPIKey respectively.
## NOTE: When it's set the previous parameters "projectId", "clusterName", "publicAPIKey" and "privateAPIKey" are ignored.
##
existingSecret: ""
# Connection string for MongoDB replica set deployed with Cognigy MongoDB Helm Chart into 3 availability zones:
# hosts: mongodb-0.mongodb-headless.mongodb.svc.cluster.local:27017,mongodb-1.mongodb-headless.mongodb.svc.cluster.local:27017,mongodb-2.mongodb-headless.mongodb.svc.cluster.local:27017
# Connection string for development and testing with a single replica MongoDB deployed with Cognigy MongoDB Helm Chart:
# hosts: "mongodb-0.mongodb-headless.mongodb.svc.cluster.local:27017"
# For MongoDB Atlas use the connection string of your MongoDB Atlas Cluster
hosts: mongodb-0.mongodb-headless.mongodb.svc.cluster.local:27017,mongodb-1.mongodb-headless.mongodb.svc.cluster.local:27017,mongodb-2.mongodb-headless.mongodb.svc.cluster.local:27017
## db-init generator image
##
dbinit:
image: cognigy.azurecr.io/mongodb:6.0.13-debian-11-r21
helmHook:
deletePolicy: "before-hook-creation,hook-succeeded"
securityContext: {}
affinity: {}
nodeSelector: {}
tolerations: []
## Generate MongoDB connection string for Cognigy services. Enabled by default.
## When enabled and the value of the "auth.password" is provided, "auth.password" will be used in MongoDB connection string.
## Defaults to a random 24 character alphanumeric string if not set.
## Alternatively provide the name of an existing secret with MongoDB connection string.
##
## Note: Only override the value of "dbCredentials.services.<serviceName>.password" or "dbCredentials.services.<serviceName>.existingSecret" if needed.
## Do not override anything else unless you know what you are doing.
##
dbConnectionString:
enabled: true
services:
serviceAi:
enabled: true
serviceName: service-ai
auth:
## Optionally provide the password for the MongoDB connection string for this Cognigy service.
## Defaults to a random 24 character alphanumeric string
##
password: ""
## Optionally provide the name of an existing secret with MongoDB connection string.
## The secret must have the key "connection-string" containing the proper MongoDB connection string.
## In the connection string We recommend using service name as both "user" and "dbname".
##
## Secret data example for Cognigy MongoDB Helm Chart:
## connection-string: mongodb://<user>:mongodb-0.mongodb-headless.mongodb.svc.cluster.local:27017,mongodb-1.mongodb-headless.mongodb.svc.cluster.local:27017,mongodb-2.mongodb-headless.mongodb.svc.cluster.local:27017/<dbname>
## Secret data example for MongoDB Atlas:
## connection-string: mongodb+srv://<user>:foo@<mongodb_atlas_hostname>/<dbname>
##
## NOTE: When it's set the previous parameters "password" is ignored.
##
existingSecret: ""
serviceAlexaManagement:
enabled: true
serviceName: service-alexa-management
auth:
password: ""
existingSecret: ""
serviceAnalyticsCollector:
enabled: true
serviceName: service-analytics-collector
auth:
password: ""
existingSecret: ""
serviceAnalyticsConversations:
enabled: true
serviceName: service-analytics-conversation
auth:
password: ""
existingSecret: ""
serviceApi:
enabled: true
serviceName: service-api
auth:
password: ""
existingSecret: ""
serviceAppSessionManager:
enabled: true
serviceName: service-app-session-manager
auth:
password: ""
existingSecret: ""
serviceCollaboration:
enabled: false
serviceName: service-collaboration
auth:
password: ""
existingSecret: ""
serviceCustomModules:
enabled: true
serviceName: service-custom-modules
auth:
password: ""
existingSecret: ""
serviceFunctionScheduler:
enabled: true
serviceName: service-function-scheduler
auth:
password: ""
existingSecret: ""
serviceHandover:
enabled: true
serviceName: service-handover
auth:
password: ""
existingSecret: ""
serviceHandoverInactivity:
enabled: true
serviceName: service-handover-inactivity
auth:
password: ""
existingSecret: ""
serviceInsightsResources:
enabled: false
serviceName: service-insights-resources
auth:
password: ""
existingSecret: ""
serviceLogs:
enabled: true
serviceName: service-logs
auth:
password: ""
existingSecret: ""
serviceNlp:
enabled: true
serviceName: service-nlp
auth:
password: ""
existingSecret: ""
serviceProfiles:
enabled: true
serviceName: service-profiles
auth:
password: ""
existingSecret: ""
serviceResources:
enabled: true
serviceName: service-resources
auth:
password: ""
existingSecret: ""
serviceRuntimeFileManager:
enabled: true
serviceName: service-runtime-file-manager
auth:
password: ""
existingSecret: ""
serviceSecurity:
enabled: true
serviceName: service-security
auth:
password: ""
existingSecret: ""
serviceTaskManager:
enabled: true
serviceName: service-task-manager
auth:
password: ""
existingSecret: ""
serviceTrainer:
enabled: true
serviceName: service-trainer
auth:
password: ""
existingSecret: ""
agentAssistBackend:
enabled: true
serviceName: agent-assist
auth:
password: ""
existingSecret: ""
## Credentials for pulling image from private image registry.
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
## NOTE 1: Either clear text credentials (registry, username and password) or pullSecrets must be provided.
## NOTE 2: If traefik is enabled and you provide clear text credentials, then traefik.deployment.imagePullSecrets must
## be set to "cognigy-registry-token". If you set custom pullSecrets value instead, set the same value under traefik.deployment.imagePullSecrets
imageCredentials:
## Alternatively specify the username, password and the url of the private registry.
## A kubernetes.io/dockerconfigjson type secret named "cognigy-registry-token" will be created based on these information.
registry: "cognigy.azurecr.io"
username: ""
password: ""
## Alternatively specify an array of imagePullSecrets.
## Secrets must be manually created in the proper namespace beforehand.
## Example:
## pullSecrets:
## - cognigyRegistrySecretName
##
## NOTE: When registry, username and password all are set, the pullSecrets are ignored.
pullSecrets: []
# Cognigy supports 3 cloud providers:
# - aws
# - azure
# - generic for on-premises installation e.g. with OpenShift
cloud:
provider: aws
region: ""
## flow-modules ReadWriteMany PVC
##
flowModules:
## Persistence parameters
##
## Enable persistence using Persistent Volume Claims
## ref: https://kubernetes.io/docs/user-guide/persistent-volumes/
##
persistence:
## For AWS cloud provider only
##
aws:
## Optionally specify the parameters of an existing Elastic File System or EFS
## ref: https://aws.amazon.com/efs/
## Note: By default this is enabled for the AWS cloud provider. When enabled, the value of the efs ID must be provided
##
efs:
enabled: true
## EFS File system ID
##
id: ""
## Enable efs csi driver
## ref: https://github.com/kubernetes-sigs/aws-efs-csi-driver
## Note: By default this is disabled, if enabled then provide the directoryPerms, uid and gid. The default value of directoryPerms, uid and gid are 777, 1000 and 1000 respectively
efs_csi:
enabled: false
directoryPerms: ""
uid: ""
gid: ""
## Optionally specify StorageClass for flowModules data volume
## If defined, storageClassName: <storageClass>
## If undefined or set to null, storageClassName is set according to the value defined in "cloud.provider"
##
storageClass: ""
## PVC Storage Request for flowModules data volume.
## Default value for AWS is 1Mi and for Azure 100Gi
## Note: The storage request has no effect for NFS
##
size: ""
## functions ReadWriteMany PVC
##
functions:
## Persistence parameters
##
## Enable persistence using Persistent Volume Claims
## ref: https://kubernetes.io/docs/user-guide/persistent-volumes/
##
persistence:
## For AWS cloud provider only
##
aws:
## Optionally specify the parameters of an existing Elastic File System or EFS
## ref: https://aws.amazon.com/efs/
## Note: By default this is enabled for the AWS cloud provider. When enabled, the value of the efs ID must be provided
##
efs:
enabled: true
## EFS File system ID
##
id: ""
## Enable efs csi driver
## ref: https://github.com/kubernetes-sigs/aws-efs-csi-driver
## Note: By default this is disabled, if enabled then provide the directoryPerms, uid and gid. The default value of directoryPerms, uid and gid are 777, 1000 and 1000 respectively
efs_csi:
enabled: false
directoryPerms: ""
uid: ""
gid: ""
## Optionally specify StorageClass for functions data volume
## If defined, storageClassName: <storageClass>
## If undefined or set to null, storageClassName is set according to the value defined in "cloud.provider"
##
storageClass: ""
## PVC Storage Request for functions data volume.
## Default value for aws is 1Mi and for azure 100Gi
## Note: The storage request has no effect for NFS
##
size: ""
## !!! Deprecation Warning !!!
## This "efs" section will be deprecated in the future release.
## Please use/migrate to "flowModules.persistence.aws.efs.id" and "functions.persistence.aws.efs.id" instead.
##
## For AWS cloud provider only:
##
efs:
flowModules:
id: ""
functions:
id: ""
cognigyLiveAgent:
## Define the value of the API token. Defaults to a random 24 characters alphanumeric string
##
platformToken: ""
## Existing secret with live-agent credentials. The secret must have the following key:
## "cognigy-live-agent-platform-token": The token for cognigy live agent
##
## NOTE: When cognigyLiveAgent.existingSecret is set, clear text token passed in the previous parameter
## "cognigyLiveAgent.platformToken" is ignored.
existingSecret: ""
# The API access token for Agent Assist Workspace API requests authentication
# These requests include the config and tile updates defined in the Agent Assist flows containing Agent Assist flow nodes.
cognigyAgentAssist:
# Set to true to enable Agent Assist Workspace
enabled: false
# Set it to true to use the Genesys Notification Forwarder
enableGenesysNotificationsForwarder: false
accessToken: ""
## Existing secret with agent-assist credentials. The secret must have the following key:
## "api-access-token": The access token for cognigy agent assist
##
## NOTE: When cognigyAgentAssist.existingSecret is set, clear text token passed in the previous parameter
## "cognigyAgentAssist.accessToken" is ignored.
existingSecret: ""
# Install Management UI on the cluster.
# It is not required, since if not installed and the API endpoint is accessible from the Internet, you can still use Cognigy Management UI at https://management-ui-v4.cognigy.ai/
managementUi:
enabled: false
ingress:
enabled: true
host: ""
tls:
enabled: false
existingSecret: ""
crt: ""
key: ""
ipWhiteListMiddleware:
enabled: true
ipWhiteList:
sourceRange:
- 0.0.0.0/0
ipStrategy:
depth: 0
image: cognigy.azurecr.io/management-ui:release-0e45409099-1736525341
replicaCount: 1
resources:
limits:
memory: "30Mi"
cpu: "20m"
requests:
memory: "10Mi"
cpu: "10m"
extraEnvVars: []
securityContext: {}
affinity: {}
nodeSelector: {}
tolerations: []
priorityClassName: ""
## managementUiCredentials: '[{"username": "example_username", "password": "example_password"}]'
managementUiCredentials: "[]"
## The name of an existing secret with management UI credentials. The secret must have a
## "management-ui-creds.json" key from where the password will be extracted and the content of that key
## should be in the following format-
## [{"username": "user", "password": "pass"}, {"username": "user2", "password": "pass2"}]
## NOTE: When this is set, clear text credentials passed in the variable "managementUiCredentials" is ignored.
managementUiCredentialsExistingSecret: ""
## SMTP server information for 'forgot password' functionality.
## Password for the SMTP server.
## A secret named "cognigy-smtp" will be created based on the information provided.
smtpPassword: ""
## The name of an existing secret with SMTP server credentials. The secret must have a
## "system-smtp-password" key from where the password will be extracted.
## NOTE: When this is set, "smtpPassword" is ignored.
smtpPasswordExistingSecret: ""
amazonCredentials:
## The client id from amazon.developers.com
clientId: ""
## The client secret from amazon.developers.com
clientSecret: ""
## Existing secret with amazon credentials. The secret must have the following two keys:
## "amazon-client-id": The client id from amazon.developers.com
## "amazon-client-secret": The client secret from amazon.developers.com
##
## NOTE: When amazonCredentials.existingSecret is set, clear text credentials passed in the previous parameters
## "amazonCredentials.clientId" and "amazonCredentials.clientSecret" are ignored.
existingSecret: ""
smtpOAuth2:
auth:
## The client id from your email client oauth2 credentials
clientId: ""
## The client secret from your email client oauth2 credentials
clientSecret: ""
refreshToken: ""
accessToken: ""
## The name of an existing secret with SMTP OAuth2 credentials.
## The secret must contain "smtp-oauth2-client-id", "smtp-oauth2-client-secret", "smtp-oauth2-refresh-token" and "smtp-oauth2-access-token" keys.
##
## Example secret data format:
##
## smtp-oauth2-client-id: <smtp-oauth2-client-id>
## smtp-oauth2-client-secret: <smtp-oauth2-client-secret>
## smtp-oauth2-refresh-token: <smtp-oauth2-refresh-token>
## smtp-oauth2-access-token: <smtp-oauth2-access-token>
##
## NOTE: When it's set, the previous "smtpOAuth2.auth.clientId, smtpOAuth2.auth.clientSecret, smtpOAuth2.auth.refreshToken, smtpOAuth2.auth.accessToken" parameters are ignored.
##
existingSecret: ""
smtpEmailNotificationCredentials:
## The default authentication type value is set to 'basic', and depending on it credentials will be used
## for sending emails based on authentication succeeds or fails.
## The basic/oauth2 parameters can be empty, the application code handles the logic.
authType: "basic"
basic:
## The username and password for your email client basic credentials
username: ""
password: ""
oauth2:
## The oauth2 user, for example in case of Gmail provider user is your gmail email Id.
user: ""
## The client id from your email client oauth2 credentials
clientId: ""
## The client secret from your email client oauth2 credentials
clientSecret: ""
## This token when provided, is used to refresh or fetch the new acces token, when access token is invalid/expires
refreshToken: ""
## This token is used for authorization email request and is of type 'Bearer'
accessToken: ""
## The name of an existing secret with SMTP Email Notification credentials.
## When the authType is 'basic', secret must contain "smtp-email-basic-username" and "smtp-email-basic-password" keys.
## When the authType is 'oauth2', secret must contain "smtp-email-oauth2-user", "smtp-email-oauth2-client-id", "smtp-email-oauth2-client-secret", "smtp-email-oauth2-access-token" and "smtp-email-oauth2-refresh-token" keys.
##
## Example secret data format, when authType: 'basic':
##
## smtp-email-basic-username: <smtp-email-basic-username>
## smtp-email-basic-password: <smtp-email-basic-password>
##
## Example secret data format, when authType: 'oauth2':
##
## smtp-email-oauth2-user: <smtp-email-oauth2-user>
## smtp-email-oauth2-client-id: <smtp-email-oauth2-client-id>
## smtp-email-oauth2-client-secret: <smtp-email-oauth2-client-secret>
## smtp-email-oauth2-access-token: <smtp-email-oauth2-access-token>
## smtp-email-oauth2-refresh-token: <smtp-email-oauth2-refresh-token>
##
## NOTE: When authType is 'basic' and 'existingSecret' is set, the previous "smtpEmailNotificationCredentials.basic.username, smtpEmailNotificationCredentials.basic.password" parameters are ignored.
## NOTE: When authType is 'oauth2' and 'existingSecret' is set, the previous "smtpEmailNotificationCredentials.oauth2.user, smtpEmailNotificationCredentials.oauth2.clientId, smtpEmailNotificationCredentials.oauth2.clientSecret, smtpEmailNotificationCredentials.oauth2.refreshToken, smtpEmailNotificationCredentials.oauth2.accessToken" parameters are ignored.
##
existingSecret: ""
commonSecrets:
## Additional facebook configuration. This is to verify the token in the webhook
##
cognigyFacebook:
## Define the value of the token. Defaults to base 16 of a random 16 character alphanumeric string
##
token: ""
## Optionally provide the name of an existing secret containing facebook verify token. The secret must contain
## the key "fb-verify-token" that contains the value of the token.
##
## NOTE: When it's set the previous parameter "commonSecrets.cognigyFacebook.token" is ignored.
##
existingSecret: ""
## API key for Cognigy insights service collector
##
cognigyInsightsCollectorApiKey:
## Define the value of the API key. Defaults to base 16 of a random 128 character alphanumeric string
##
token: ""
## Optionally provide the name of an existing secret containing API key. The secret must contain
## the key "secret" that contains the value of the API key.
##
## NOTE: When it's set the previous parameter "commonSecrets.cognigyInsightsCollectorApiKey.token" is ignored.
##
existingSecret: ""
## Cognigy Collaboration JWT token
##
cognigyCollaborationJwt:
## Define the value of the JWT token. Defaults to base 16 of a random 128 character alphanumeric string
##
token: ""
## Optionally provide the name of an existing secret containing JWT token. The secret must contain
## the key "secret" that contains the value of the JWT token.
##
## NOTE: When it's set the previous parameter "commonSecrets.cognigyCollaborationJwt.token" is ignored.
##
existingSecret: ""
## Cognigy Insights JWT token
##
cognigyInsightsJwt:
## Define the value of the JWT token. Defaults to base 16 of a random 128 character alphanumeric string
##
token: ""
## Optionally provide the name of an existing secret containing JWT token. The secret must contain
## the key "secret" that contains the value of the JWT token.
##
## NOTE: When it's set the previous parameter "commonSecrets.cognigyInsightsJwt.token" is ignored.
##
existingSecret: ""
## The JWT secret to sign JWT-tokens with, this is used e.g. for realtime-tokens (endpoint, backend connection)
##
cognigyJwt:
## Define the value of the JWT token. Defaults to base 16 of a random 128 character alphanumeric string
##
token: ""
## Optionally provide the name of an existing secret containing JWT token. The secret must contain
## the key "secret" that contains the value of the JWT token.
##
## NOTE: When it's set the previous parameter "commonSecrets.cognigyJwt.token" is ignored.
##
existingSecret: ""
## Verify token for RCE
##
cognigyRceCredentials:
## Define the value of the JWT token. Defaults to base 16 of a random 32 character alphanumeric string
##
token: ""
## Optionally provide the name of an existing secret containing JWT token. The secret must contain
## the key "rce-verify-token" that contains the value of the JWT token.
##
## NOTE: When it's set the previous parameter "commonSecrets.cognigyRceCredentials.token" is ignored.
##
existingSecret: ""
## OData API key
##
cognigyOdata:
## Define the value of the API key. Defaults to base 16 of a random 32 character alphanumeric string
##
token: ""
## Optionally provide the name of an existing secret containing API key. The secret must contain
## the key "odata-super-api-key" that contains the value of the API key.
##
## NOTE: When it's set the previous parameter "commonSecrets.cognigyOdata.token" is ignored.
##
existingSecret: ""
## The Cognigy Service Endpoint secret access token
##
cognigyServiceEndpointApiAccessToken:
## Define the value of the API token. Defaults to base 16 of a random 16 character alphanumeric string
##
token: ""
## Optionally provide the name of an existing secret containing API token. The secret must contain
## the key "api-access-token" that contains the value of the API token.
##
## NOTE: When it's set the previous parameter "commonSecrets.cognigyServiceEndpointApiAccessToken.token" is ignored.
##
existingSecret: ""
## The Cognigy Service Handover secret access token
##
cognigyServiceHandoverApiAccessToken:
## Define the value of the API token. Defaults to base 16 of a random 16 character alphanumeric string
##
token: ""
## Optionally provide the name of an existing secret containing API token. The secret must contain
## the key "api-access-token" that contains the value of the API token.
##
## NOTE: When it's set the previous parameter "commonSecrets.cognigyServiceHandoverApiAccessToken.token" is ignored.
##
existingSecret: ""
cognigySearchOrchestratorApiKey:
## Define the value of the API token. Defaults to base 16 of a random 16 character alphanumeric string
##
token: ""
## Optionally provide the name of an existing secret containing API token. The secret must contain
## the key "api-key" that contains the value of the API token.
##
## NOTE: When it's set the previous parameter "commonSecrets.cognigySearchOrchestratorApiKey.token" is ignored.
##
existingSecret: ""
cognigySecureFormsApiKey:
## Define the value of the API token. Defaults to empty string
##
token: ""
## Optionally provide the name of an existing secret containing API token. The secret must contain
## the key "api-key" that contains the value of the API token.
##
## NOTE: When it's set the previous parameter "commonSecrets.cognigySecureFormsApiKey.token" is ignored.
##
existingSecret: ""
cognigyOauthClientSecret:
## Define the value of the Oauth Client Secret. Defaults to a random 64 character alphanumeric string
##
token: ""
## Optionally provide the name of an existing secret containing the client secret. The secret must contain
## the key "secret" that contains the value of the secret.
##
## NOTE: When it's set the previous parameter "commonSecrets.cognigyOauthClientSecret.token" is ignored.
##
existingSecret: ""
cognigyVoicegatewayClientSecret:
## Define the value of the Oauth Client Secret. Defaults to a random 64 character alphanumeric string
## The value of this secret should be same as the client secret created in VoiceGateway Cluster
##
token: ""
## Optionally provide the name of an existing secret containing the client secret. The secret must contain
## the key "secret" that contains the value of the secret.
##
## NOTE: When it's set the previous parameter "commonSecrets.cognigyVoicegatewayClientSecret.token" is ignored.
##
existingSecret: ""
vgWebappDefaultLoginCredentials:
## Define the value of the Voice Gateway WebApp Login Credentials. Defaults to an empty username and password in json format.
## The value of this secret should be same as the login credential secret created in VoiceGateway Cluster
## The value consists of JSON {"username": "example_username", "password": "example_password"}
##
credential: '{"username": "", "password": ""}'
## Optionally provide the name of an existing secret containing the credential. The secret must contain
## the key "vg-webapp-login-creds" that contains the value in the above format
##
## NOTE: When it's set the previous parameter "commonSecrets.vgWebappDefaultLoginCredentials.vg-webapp-login-creds" is ignored.
##
existingSecret: ""
## Optionally provide podAnnotations for all deployments except dependency charts.
cognigyCommonPodAnnotations: {}
# This is a temporary flag for the "Knowledge Search" feature. It be removed once
# feature development is complete. Please DO NOT use this flag for now if you are a
# customer running Cognigy.AI/Cognigy Insights using this HelmChart.
knowledgeSearch:
enabled: false
# System-wide Azure AI Document Intelligence configuration
globalAzureDocumentIntelligenceConfig:
# Enabling this will only take effect when the parent
# 'knowledgeSearch'feature is enabled.
enabled: false
## The API key for Azure AI Document Intelligence
apiKey: ""
## The endpoint URL for Azure AI Document Intelligence
endpointUrl: ""
## Existing secret with azureDocIntel credentials. The secret must have the following two keys:
## "azureDocIntel-api-key": The API key for Azure AI Document Intelligence
## "azureDocIntel-endpoint-url": The endpoint URL for Azure AI Document Intelligence
##
## NOTE: When globalAzureDocumentIntelligenceConfig.existingSecret is set, clear text credentials passed in the previous parameters
## "globalAzureDocumentIntelligenceConfig.api-key" and "globalAzureDocumentIntelligenceConfig.endpoint-url" are ignored.
existingSecret: ""
## Traefik TLS certificate for the hostname defined at ingress.<service_name>.host
## NOTE: If you provide "tls.enable: true" and "traefik.enabled: true", either tls.crt and tls.key or tls.existingSecret must be provided.
tls:
## Enable traefik tls
## NOTE: If traefik is enabled ("traefik.enabled: true"), and you provide "tls.enable: false", then the auto redirection of http to https
## also must be disabled by setting traefik.ports.web.redirectTo.port: null
enabled: true
## Add Custom CA certificate. A tls type secret named "cognigy-traefik" will be created based on the values of tls.crt and tls.key
## Careful with the indentation
## For more information, see https://helm.sh/docs/chart_template_guide/yaml_techniques/#strings-in-yaml
##
## Custom CA certificate in plaintext, not base64 encoded.
## Example:
## crt: |
## -----BEGIN CERTIFICATE-----
## -----END CERTIFICATE-----
crt: ""
## CA certificate private key in plaintext, not base64 encoded.
## Example:
## key: |
## -----BEGIN PRIVATE KEY-----
## -----END PRIVATE KEY-----
key: ""
## Existing secret with TLS certificates. The secret must have the following two keys:
## "tls.crt": Containing the CA certificate
## "tls.key": Containing the certificate key
## NOTE: When tls.existingSecret is set, clear text certificate passed in the previous parameters "tls.crt" and "tls.key" are ignored.
existingSecret: ""
# If ingress is not required to deploy then you can set "ingress.enabled" to false. By default it is always enabled.
# ingress:
# enabled: false
ingress:
enabled: true
serviceAnalyticsOdata:
host: ""
## Do not use ingress.<service>.tls.enabled parameter if you have a wildcard certificate for all ingresses (recommended), use `tls` section for a wildcard certificate instead.
## If you have individual certificates per ingress, set ingress.<service>.tls.enabled: "true" per individual ingress.
## This will create a new secret cognigy-<service-name>-tls containing the individual certificate and the ingress will be served with the individual certificate.
## You will need to provide the certificate either in clear text by setting `crt` and `key` fields or as existing base64-encoded kubernetes secret.
## For a TLS certificate in clear text set:
## "ingress.<service>.tls.crt": TLS certificate including full certificate chain
## "ingress.<service>.tls.key": TLS certificate key
## NOTE: When ingress.<service>.tls.existingSecret is set, certificate in clear text under `tls.crt` and `tls.key` is ignored.
## Please make sure the `existingSecret` is created before referencing it in the ingress specification
## CA certificate and certificate key in plaintext, not base64 encoded.
## Example:
## key: |
## -----BEGIN PRIVATE KEY-----
## -----END PRIVATE KEY-----
tls:
enabled: false
existingSecret: ""
crt: ""
key: ""
## Traefik IPWhiteList middleware. IPWhitelist accepts / refuses requests based on the client IP.
## A sourceRange of 0.0.0.0/0 means all IPs are allowed. For more detail https://doc.traefik.io/traefik/middlewares/http/ipwhitelist/
ipWhiteListMiddleware:
enabled: true
ipWhiteList:
sourceRange:
- 0.0.0.0/0
ipStrategy:
depth: 0
serviceApi:
host: ""
tls:
enabled: false
existingSecret: ""
crt: ""
key: ""
ipWhiteListMiddleware:
enabled: true
ipWhiteList:
sourceRange:
- 0.0.0.0/0
ipStrategy:
depth: 0
serviceAppSessionManager:
host: ""
tls:
enabled: false
existingSecret: ""
crt: ""
key: ""
ipWhiteListMiddleware:
enabled: true
ipWhiteList:
sourceRange:
- 0.0.0.0/0
ipStrategy:
depth: 0
serviceCollector:
host: ""
tls:
enabled: false
existingSecret: ""
crt: ""
key: ""
ipWhiteListMiddleware:
enabled: true
ipWhiteList:
sourceRange:
- 0.0.0.0/0
ipStrategy:
depth: 0
serviceEndpoint:
host: ""
tls:
enabled: false
existingSecret: ""
crt: ""
key: ""
ipWhiteListMiddleware:
enabled: true
ipWhiteList:
sourceRange:
- 0.0.0.0/0
ipStrategy:
depth: 0
serviceInsightsApi:
host: ""
tls:
enabled: false
existingSecret: ""
crt: ""
key: ""
ipWhiteListMiddleware:
enabled: true
ipWhiteList:
sourceRange:
- 0.0.0.0/0
ipStrategy:
depth: 0
serviceRuntimeFileManager:
host: ""
tls:
enabled: false
existingSecret: ""
crt: ""
key: ""
ipWhiteListMiddleware:
enabled: true
ipWhiteList:
sourceRange:
- 0.0.0.0/0
ipStrategy:
depth: 0
serviceUi:
host: ""
tls:
enabled: false
existingSecret: ""
crt: ""
key: ""
ipWhiteListMiddleware:
enabled: true
ipWhiteList:
sourceRange:
- 0.0.0.0/0
ipStrategy:
depth: 0
serviceStaticFiles:
host: ""
tls:
enabled: false
existingSecret: ""
crt: ""
key: ""
ipWhiteListMiddleware:
enabled: true
ipWhiteList:
sourceRange:
- 0.0.0.0/0
ipStrategy:
depth: 0
serviceWebchat:
host: ""
tls:
enabled: false
existingSecret: ""
crt: ""
key: ""
ipWhiteListMiddleware:
enabled: true
ipWhiteList:
sourceRange:
- 0.0.0.0/0
ipStrategy:
depth: 0
agentAssistBackend:
host: ""
legacyHost: ""
tls:
enabled: false
existingSecret: ""
crt: ""
key: ""
ipWhiteListMiddleware:
enabled: true
ipWhiteList:
sourceRange:
- 0.0.0.0/0
ipStrategy:
depth: 0
agentAssistFrontend:
host: ""
legacyHost: ""
tls:
enabled: false
existingSecret: ""
crt: ""
key: ""
ipWhiteListMiddleware:
enabled: true
ipWhiteList:
sourceRange:
- 0.0.0.0/0
ipStrategy:
depth: 0
## Kubernetes service type
##
service:
serviceAnalyticsOdata:
## Optional Service annotations.
## Example:
## annotations:
## service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0
## service.name: service-analytics-odata
##
annotations: {}
serviceApi:
annotations: {}
serviceAppSessionManager:
annotations: {}
serviceCollaboration:
annotations: {}
serviceEndpoint:
annotations: {}
serviceInsightsApi:
annotations: {}
serviceCollector:
annotations: {}
serviceHandover:
annotations: {}
serviceInsightsUi:
annotations: {}
serviceRuntimeFileManager:
annotations: {}
serviceStaticFiles:
annotations: {}
serviceUi:
annotations: {}
serviceWebchat:
annotations: {}
statefulRabbitMq:
annotations: {}
serviceNlpEmbeddingEn:
annotations: {}
serviceNlpEmbeddingXx:
annotations: {}
serviceNlpEmbeddingGe:
annotations: {}
serviceSearchOrchestrator:
annotations: {}
cubeApiServer:
annotations: {}
cubeStoreRouter:
annotations: {}
cubeStoreWorker:
annotations: {}
agentAssistBackend:
annotations: {}
agentAssistFrontend:
annotations: {}
agentAssistGenesysNotificationsForwarder:
annotations: {}
cognigyEnv:
NODE_ENV: production
## This feature flag when activated disables the "resetting of flow".
FEATURE_DISABLE_RESET_FLOW: "true"
OAUTH_CLIENT_ID: "cognigy-ui"
CLIENT_ID_COGNIGY_VOICE_GATEWAY: "voicegateway"
CLIENT_ID_COGNIGY_LIVE_AGENT: "cognigy-live-agent"
# Enable the creation of metrics which will then get consumed
# by our 'service-monitoring'.
MONITOR_RPC_CALLS: "true"
# Enable Redis Sentinel (HA mode)
FEATURE_REDIS_SENTINEL_MODE_ENABLED: "true"
REDIS_SENTINEL_MASTER_NAME: "mymaster"
REDIS_SENTINEL_HOST: "redis-ha-headless"
REDIS_SENTINEL_PORT: "26379"
# Enable Redis Persistent Sentinel (HA mode)
FEATURE_REDIS_PERSISTENT_SENTINEL_MODE_ENABLED: "true"
REDIS_PERSISTENT_SENTINEL_MASTER_NAME: "mymaster"
REDIS_PERSISTENT_SENTINEL_HOST: "redis-persistent-ha-headless"
REDIS_PERSISTENT_SENTINEL_PORT: "26379"
# limits (api requests, db queries, context-size)
MESSAGE_TTL_SECONDS: "120"
MAX_MEMORY_OBJECT_SIZE: "65536"
HTTP_JSON_BODY_LIMIT: "65536"
MAX_BYTE_SIZE: "524288"
RESPONSE_BYTES_LIMIT: "524288"
# features (enable / disable)
FEATURE_CUSTOM_NODES: "true"
# log cleanup
LOG_ENTRIES_TTL_IN_MINUTES: "1440"
LOG_ENTRIES_BUFFER_IN_SECONDS: "5"
# SMTP server for 'forgot password' functionality
SYSTEM_SMTP_HOST: "test"
SYSTEM_SMTP_PORT: "test"
SYSTEM_SMTP_USERNAME: "test"
SYSTEM_SMTP_FROM: "test"
SYSTEM_SMTP_CONNECTION_TYPE: "starttls"