Edit values.yaml

This commit is contained in:
inikulin 2025-06-03 13:44:41 +00:00
parent 2485a5c87c
commit 6a1b4ae87b

View File

@ -2192,7 +2192,194 @@ provisioning:
## max.message.bytes: 64000
## flush.messages: 1
##
topics: []
topics:
- name: test
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: notifications
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: user-events.v1
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: chat-events.v1
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: message-events.v1
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: android-pushes
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: ios-pushes
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: huawei-pushes
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: desktop-pushes
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: safari-pushes
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: web-pushes
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: big-groups-topic
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: voip
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: regular-groups-topic
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: search-chat-events.v1.dlt
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: search-user-events.v1.dlt
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: search-message-events.v1.dlt
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: message-events.v1.dlt
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: notification-unregister-tokens
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: user-sticker-events.v1
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: user-sticker-events.v1.dlt
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: external-call-events.v1.dlt
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: gem-call-lifecycle-events.v1.dlt
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: external-call-events.v1
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: gem-call-lifecycle-events.v1
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: realtime-events.v1
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: realtime-events.v1.dlt
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: livekit-events.v1
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: livekit-events.v1.dlt
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: call-events.v1
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
- name: call-events.v1.dlt
partitions: 3
replicationFactor: 3
config:
max.message.bytes: 128000
flush.messages: 10
## @param provisioning.nodeSelector Node labels for pod assignment
## Ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/
##