Kafka binding spec

Detailed documentation on the Kafka binding component

Component format

To setup Kafka binding create a component of type bindings.kafka. See this guide on how to create and apply a binding configuration. For details on using secretKeyRef, see the guide on how to reference secrets in components.

  1. apiVersion: dapr.io/v1alpha1
  2. kind: Component
  3. metadata:
  4. name: kafka-binding
  5. spec:
  6. type: bindings.kafka
  7. version: v1
  8. metadata:
  9. - name: topics # Optional. Used for input bindings.
  10. value: "topic1,topic2"
  11. - name: brokers # Required.
  12. value: "localhost:9092,localhost:9093"
  13. - name: consumerGroup # Optional. Used for input bindings.
  14. value: "group1"
  15. - name: publishTopic # Optional. Used for output bindings.
  16. value: "topic3"
  17. - name: authRequired # Required.
  18. value: "true"
  19. - name: saslUsername # Required if authRequired is `true`.
  20. value: "user"
  21. - name: saslPassword # Required if authRequired is `true`.
  22. secretKeyRef:
  23. name: kafka-secrets
  24. key: saslPasswordSecret
  25. - name: initialOffset # Optional. Used for input bindings.
  26. value: "newest"
  27. - name: maxMessageBytes # Optional.
  28. value: 1024
  29. - name: version # Optional.
  30. value: 1.0.0

Spec metadata fields

FieldRequiredBinding supportDetailsExample
topicsNInputA comma-separated string of topics.“mytopic1,topic2”
brokersYInput/OutputA comma-separated string of Kafka brokers.“localhost:9092,dapr-kafka.myapp.svc.cluster.local:9093”
clientIDNInput/OutputA user-provided string sent with every request to the Kafka brokers for logging, debugging, and auditing purposes.“my-dapr-app”
consumerGroupNInputA kafka consumer group to listen on. Each record published to a topic is delivered to one consumer within each consumer group subscribed to the topic.“group1”
consumeRetryEnabledNInput/OutputEnable consume retry by setting to “true”. Default to false in Kafka binding component.“true”, “false”
publishTopicYOutputThe topic to publish to.“mytopic”
authRequiredNDeprecatedEnable SASL authentication with the Kafka brokers.“true”, “false”
authTypeYInput/OutputConfigure or disable authentication. Supported values: none, password, mtls, or oidc“password”, “none”
saslUsernameNInput/OutputThe SASL username used for authentication. Only required if authRequired is set to “true”.“adminuser”
saslPasswordNInput/OutputThe SASL password used for authentication. Can be secretKeyRef to use a secret reference. Only required if authRequired is set to “true”.“”, “KeFg23!”
initialOffsetNInputThe initial offset to use if no offset was previously committed. Should be “newest” or “oldest”. Defaults to “newest”.“oldest”
maxMessageBytesNInput/OutputThe maximum size in bytes allowed for a single Kafka message. Defaults to 1024.2048
oidcTokenEndpointNInput/OutputFull URL to an OAuth2 identity provider access token endpoint. Required when authType is set to oidchttps://identity.example.com/v1/token”
oidcClientIDNInput/OutputThe OAuth2 client ID that has been provisioned in the identity provider. Required when authType is set to oidcdapr-kafka
oidcClientSecretNInput/OutputThe OAuth2 client secret that has been provisioned in the identity provider: Required when authType is set to oidc“KeFg23!”
oidcScopesNInput/OutputComma-delimited list of OAuth2/OIDC scopes to request with the access token. Recommended when authType is set to oidc. Defaults to “openid”“openid,kafka-prod”

Binding support

This component supports both input and output binding interfaces.

This component supports output binding with the following operations:

  • create

Authentication

Kafka supports a variety of authentication schemes and Dapr supports several: SASL password, mTLS, OIDC/OAuth2. Learn more about Kafka’s authentication method for both the Kafka binding and Kafka pub/sub components.

Specifying a partition key

When invoking the Kafka binding, its possible to provide an optional partition key by using the metadata section in the request body.

The field name is partitionKey.

Example:

  1. curl -X POST http://localhost:3500/v1.0/bindings/myKafka \
  2. -H "Content-Type: application/json" \
  3. -d '{
  4. "data": {
  5. "message": "Hi"
  6. },
  7. "metadata": {
  8. "partitionKey": "key1"
  9. },
  10. "operation": "create"
  11. }'

Response

An HTTP 204 (No Content) and empty body will be returned if successful.

Last modified July 27, 2022: Remove namespace element from component examples (#2647) (ff9de5c8)