VirtualClusterNamespaceTopicSelector
objectOne OfAllowed values:glob
Expose any backend topic that matches this glob pattern (e.g., operations_data_*).
Match pattern:^[A-Za-z0-9._?*-]+$
>= 1 characters
How to inform the user about conflicts where multiple backend topics would map to the same virtual topic name.
- warn - log in the Event Gateway logs. Additionally, it sets knep_namespace_topic_conflict to 1.
- ignore - do not do anything. It does not cause knep_namespace_topic_conflict metric to be set to 1.
Allowed values:warnignore
Default:warn
VirtualClusterNamespaceTopicSelectorGlob
objectAllowed values:glob
Expose any backend topic that matches this glob pattern (e.g., operations_data_*).
Match pattern:^[A-Za-z0-9._?*-]+$
>= 1 characters
How to inform the user about conflicts where multiple backend topics would map to the same virtual topic name.
- warn - log in the Event Gateway logs. Additionally, it sets knep_namespace_topic_conflict to 1.
- ignore - do not do anything. It does not cause knep_namespace_topic_conflict metric to be set to 1.
Allowed values:warnignore
Default:warn
VirtualClusterNamespaceTopicSelectorExactList
objectAllowed values:exact_list
Explicit allow-list of backend topic names.
>= 1 items
Show Child Parameters
How to inform the user about conflicts where multiple backend topics would map to the same virtual topic name.
- warn - log in the Event Gateway logs. Additionally, it sets knep_namespace_topic_conflict to 1.
- ignore - do not do anything. It does not cause knep_namespace_topic_conflict metric to be set to 1.
Allowed values:warnignore
Default:warn
NamespaceExactAllowListItem
object>= 1 characters
VirtualClusterNamespaceIdSelector
objectOne OfAllowed values:glob
Expose any id that matches this glob pattern (e.g., my_id_*).
Match pattern:^[A-Za-z0-9._?*-]+$
>= 1 characters