Confluent

Enterprise only Premium Partner
Related Documentation
Made by
Kong Inc.
Supported Gateway Topologies
hybrid db-less traditional
Supported Konnect Deployments
hybrid cloud-gateways serverless
Compatible Protocols
grpc grpcs http https
Priority
752
Minimum Version
Kong Gateway - 3.8
Related Resources

3.15.0.5

Release date 2026/08/24

Bugfix

  • Fixed a permanent failure that started when a broker answered an ApiVersions request with an error code, an empty API key set, or a malformed frame. The client cached that result and every later request failed with ProduceRequest API version not negotiated; broker may be unreachable until the node restarted, even after the broker recovered. The client now refuses an unusable ApiVersions response, keeps the previous negotiation, and retries the negotiation for a topic whose metadata is already cached.

  • Fixed the confluent schema registry client caching fetched schemas and subjects under keys that did not account for the registry URL or authentication. Instances configured with different credentials could be served each other’s cached lookups, letting an unauthorized instance bypass schema-registry authentication once any authorized instance had warmed the cache. Cache entries are now scoped to the registry identity, and the configured schema_registry.confluent.ttl is now applied to these cache entries.

  • Fixed a crash that occurred when a plugin set schema_registry.confluent.authentication.mode to oauth2 but omitted the oauth2_client record. Previously this returned a 500 from the Admin API during validation, and once saved it also crashed at runtime while fetching the schema registry OAuth2 token. The absent oauth2_client is now handled and falls back to the default authentication method, so a configuration without oauth2_client works end-to-end.

  • Fixed an issue where OAuth2 authentication against Confluent Cloud Schema Registry failed because the client did not send the required target-sr-cluster header.

3.15.0.0

Release date 2026/07/02

Feature

  • Added support for forwarding HTTP request headers as native Kafka record headers.

  • Added SASL OAUTHBEARER authentication support.

3.14.0.14

Release date 2026/08/26

Bugfix

  • Fixed a permanent failure that started when a broker answered an ApiVersions request with an error code, an empty API key set, or a malformed frame. The client cached that result and every later request failed with ProduceRequest API version not negotiated; broker may be unreachable until the node restarted, even after the broker recovered. The client now refuses an unusable ApiVersions response, keeps the previous negotiation, and retries the negotiation for a topic whose metadata is already cached.

  • Fixed an issue where OAuth2 authentication against Confluent Cloud Schema Registry failed because the client did not send the required target-sr-cluster header.

3.14.0.10

Release date 2026/07/29

Bugfix

  • Fixed a crash that occurred when a plugin set schema_registry.confluent.authentication.mode to oauth2 but omitted the oauth2_client record. Previously this returned a 500 from the Admin API during validation, and once saved it also crashed at runtime while fetching the schema registry OAuth2 token. The absent oauth2_client is now handled and falls back to the default authentication method, so a configuration without oauth2_client works end-to-end.

3.14.0.0

Release date 2026/04/07

Feature

  • the security.ssl_verify option is now enabled by default.

3.13.0.10

Release date 2026/08/20

Bugfix

  • Fixed a crash that occurred when a plugin set schema_registry.confluent.authentication.mode to oauth2 but omitted the oauth2_client record. Previously this returned a 500 from the Admin API during validation, and once saved it also crashed at runtime while fetching the schema registry OAuth2 token. The absent oauth2_client is now handled and falls back to the default authentication method, so a configuration without oauth2_client works end-to-end.

  • Fixed an issue where OAuth2 authentication against Confluent Cloud Schema Registry failed because the client did not send the required target-sr-cluster header.

3.13.0.0

Release date 2025/12/18

Feature

  • added new config option ssl_verify to support verifying server certificates. Added support for the tls_certificate_verify global option. When this option is enabled, the plugin’s ssl_verify setting cannot be disabled.

Bugfix

  • Fixed an issue where forward_body dropped request bodies larger than Nginx’s default buffer size (16 KB). It now reads up to 1 MB and returns an error if the body can’t be fully read.

3.12.0.12

Release date 2026/09/02

Bugfix

  • Fixed a permanent failure that started when a broker answered an ApiVersions request with an error code, an empty API key set, or a malformed frame. The client cached that result and every later request failed with ProduceRequest API version not negotiated; broker may be unreachable until the node restarted, even after the broker recovered. The client now refuses an unusable ApiVersions response, keeps the previous negotiation, and retries the negotiation for a topic whose metadata is already cached.

3.12.0.11

Release date 2026/08/18

Bugfix

  • Fixed a crash that occurred when a plugin set schema_registry.confluent.authentication.mode to oauth2 but omitted the oauth2_client record. Previously this returned a 500 from the Admin API during validation, and once saved it also crashed at runtime while fetching the schema registry OAuth2 token. The absent oauth2_client is now handled and falls back to the default authentication method, so a configuration without oauth2_client works end-to-end.

3.12.0.9

Release date 2026/07/22

Bugfix

  • Fixed Kafka keepalive pools leaking connections across different SASL credentials and TLS verification settings.

3.12.0.0

Release date 2025/10/01

Bugfix

  • Fixed an issue where the plugin did not use conf.cluster_name.

3.11.0.0

Release date 2025/07/03

Feature

  • Added support for sending messages with dynamic keys to determine partitions.

3.10.0.18

Release date 2026/08/31

Bugfix

  • Fixed a permanent failure that started when a broker answered an ApiVersions request with an error code, an empty API key set, or a malformed frame. The client cached that result and every later request failed with ProduceRequest API version not negotiated; broker may be unreachable until the node restarted, even after the broker recovered. The client now refuses an unusable ApiVersions response, keeps the previous negotiation, and retries the negotiation for a topic whose metadata is already cached.

3.10.0.0

Release date 2025/03/27

Feature

  • Added support for message manipulation with the new configuration field message_by_lua_functions.

  • Added support for sending messages to multiple topics with topics_query_arg, and enabled topic allowlisting with allowed_topics.

3.8.0.0

Release date 2024/09/11

Feature

  • Added the confluent plugin which allows to interface with Confluent.

Help us make these docs great!

Kong Developer docs are open source. If you find these useful and want to make them better, contribute today!