CertificateMetadata
objectMetadata extracted from a certificate.
The issuer of the certificate.
The subject of the certificate.
The key usages of the certificate.
The expiry date of the certificate as a unix timestamp.
The Subject Alternative Names (SAN) of the certificate.
The DNS names in the certificate SAN.
The email addresses in the certificate SAN.
The IP addresses in the certificate SAN.
The URIs in the certificate SAN.
The SHA-256 fingerprint of the certificate.
EventGatewayNodeError
objectAn error reported by an event gateway node.
The name of the error.
The error message.
VirtualClusterNamespace
objectNamespace allows to implement multitenancy using a single backend cluster.
It allows to either hide or enforce a static prefix on resources (topics, consumer group IDs, transaction IDs).
- hide_prefix - the configured prefix is hidden from clients for topics and IDs when reading.
Created resources are written with the prefix on the backend cluster. - enforce_prefix - the configured prefix remains visible to clients.
Created resources must include the prefix or the request will fail.
Allowed values:hide_prefixenforce_prefix
The namespace is differentiated by this chosen prefix.
For example, if the prefix is set to “analytics_” the topic named “analytics_user_clicks” is available to the clients
of the virtual cluster. Topics without the prefix will be ignored unless added via additional.topics.
>= 1 characters
Show Child Parameters
VirtualClusterNamespaceAdditionalProperties
objectOne OfAdditional backend topics to expose even if they don’t match the namespace prefix.
The topics are not affected by the hide/enforce prefix mode.
If the client tries to create a topic that matches this list, the request is rejected.
Show Child Parameters
One OfConsumer group IDs to expose even if they don’t start with the namespace prefix.
Show Child Parameters
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