From c4f079248c50a5687548b5a9f1f8986340d93030 Mon Sep 17 00:00:00 2001 From: Kat Batuigas Date: Thu, 9 Jul 2026 15:24:39 -0700 Subject: [PATCH 1/2] Update client compatibility --- modules/develop/pages/kafka-clients.adoc | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/modules/develop/pages/kafka-clients.adoc b/modules/develop/pages/kafka-clients.adoc index 72b319eac3..7b41602c78 100644 --- a/modules/develop/pages/kafka-clients.adoc +++ b/modules/develop/pages/kafka-clients.adoc @@ -9,7 +9,7 @@ :learning-objective-2: Identify unsupported Kafka features when integrating with Redpanda // tag::single-source[] -Redpanda is compatible with Apache Kafka® versions 0.11 and later, with specific exceptions noted on this page. +Apache Kafka® clients developed for Kafka protocol version 0.11 or later work with Redpanda with minimal or no changes to your application. This page identifies which clients are validated and calls out any exceptions. Use this reference to: @@ -18,7 +18,7 @@ Use this reference to: == Kafka client compatibility -Clients developed for Kafka versions 0.11 or later are compatible with Redpanda. The Apache Kafka Java client at version 4.x is validated against Redpanda using the ducktape and chaos test suites; other clients in the table here remain compatible with the Kafka protocol versions they have always supported. Modern clients auto-negotiate protocol versions or use an earlier protocol version accepted by Redpanda brokers. +Redpanda validates the Apache Kafka Java client and a set of widely used non-Java clients, at their current versions that support Kafka 4.x, using the ducktape and chaos test suites. Validation confirms connectivity and correctness (for example, produce, consume, and transaction operations) at current client versions. It doesn't imply broker feature parity with Kafka. Modern clients auto-negotiate protocol versions or use an earlier protocol version accepted by Redpanda brokers. TIP: Always use the latest supported version of a Kafka client. @@ -31,13 +31,17 @@ The following clients have been validated with Redpanda. | https://github.com/apache/kafka[Apache Kafka Java Client^] | C/C{pp} -| https://github.com/edenhill/librdkafka[librdkafka^] +| https://github.com/confluentinc/librdkafka[librdkafka^] | Go -| https://github.com/twmb/franz-go[franz-go^] +a| +* https://github.com/twmb/franz-go[franz-go^] +* https://github.com/confluentinc/confluent-kafka-go[confluent-kafka-go^] | Python -| https://pypi.org/project/kafka-python-ng[kafka-python-ng^] +a| +* https://github.com/dpkp/kafka-python[kafka-python^] +* https://github.com/confluentinc/confluent-kafka-python[confluent-kafka-python^] | Rust | https://github.com/kafka-rust/kafka-rust[kafka-rust^] @@ -49,7 +53,7 @@ a| |=== -Clients that have not been validated by Redpanda Data, but use the Kafka protocol, remain compatible with Redpanda subject to the limitations in the next section (particularly those based on librdkafka, such as confluent-kafka-dotnet or confluent-python). +Clients that have not been validated by Redpanda Data, but use the Kafka protocol, remain compatible with Redpanda subject to the limitations in the next section (particularly those based on librdkafka, such as confluent-kafka-dotnet). If you find a client that does not work with Redpanda, reach out in the https://redpanda.com/slack[Redpanda community Slack^]. From bc6fd653f9efbddaf23e738a0b4d911e89f2884e Mon Sep 17 00:00:00 2001 From: Kat Batuigas Date: Thu, 9 Jul 2026 16:04:24 -0700 Subject: [PATCH 2/2] Add What's New --- .../pages/release-notes/redpanda.adoc | 237 +----------------- 1 file changed, 3 insertions(+), 234 deletions(-) diff --git a/modules/get-started/pages/release-notes/redpanda.adoc b/modules/get-started/pages/release-notes/redpanda.adoc index 468dccf544..22db891963 100644 --- a/modules/get-started/pages/release-notes/redpanda.adoc +++ b/modules/get-started/pages/release-notes/redpanda.adoc @@ -8,239 +8,8 @@ This topic includes new content added in version {page-component-version}. For a * xref:cloud-data-platform:get-started:cloud-overview.adoc#redpanda-cloud-vs-self-managed-feature-compatibility[Redpanda Cloud vs Self-Managed feature compatibility] -== Cloud Topics +== Kafka 4.x client compatibility -xref:develop:manage-topics/cloud-topics.adoc[Cloud Topics] are now available, making it possible to use durable cloud storage (S3, ADLS, GCS) as the primary backing store instead of local disk, eliminating over 90% of cross-AZ replication costs. This makes them ideal for latency-tolerant, high-throughput workloads such as observability streams, analytics pipelines, and AI/ML training data feeds, where cross-AZ networking charges are the dominant cost driver. +Redpanda version 26.2 validates a broader set of non-Java Apache Kafka® clients at their current versions that support Kafka 4.x, in addition to the Apache Kafka Java client. Newly validated clients include `confluent-kafka-go` for Go, and `kafka-python` and `confluent-kafka-python` for Python. Validation confirms connectivity and correctness (for example, produce, consume, and transaction operations) but does not imply broker feature parity with Kafka. -You can use Cloud Topics exclusively in Redpanda Streaming clusters, or in combination with traditional Tiered Storage and local storage topics on a shared cluster supporting low latency workloads. - -Cloud Topics require Tiered Storage and an Enterprise license. For setup instructions and limitations, see xref:develop:manage-topics/cloud-topics.adoc[]. - -== Group-based access control (GBAC) - -Redpanda {page-component-version} introduces xref:manage:security/authorization/gbac.adoc[group-based access control (GBAC)], which extends OIDC authentication to support group-based permissions. In addition to assigning roles or ACLs to individual users, you can assign them to OIDC groups. Users inherit permissions from all groups reported by their identity provider (IdP) in the OIDC token claims. - -GBAC supports two authorization patterns: - -* Assign a group as a member of an RBAC role so that all users in the group inherit the role's ACLs. -* Create ACLs directly with a `Group:` principal. - -Group membership is managed entirely by your IdP. Redpanda reads group information from the OIDC token at authentication time and works across the Kafka API, Schema Registry, and HTTP Proxy. - -== FIPS 140-3 validation and FIPS Docker image - -Redpanda's cryptographic module has been upgraded from FIPS 140-2 to https://csrc.nist.gov/pubs/fips/140-3/final[FIPS 140-3^] validation. Additionally, Redpanda now provides a FIPS-specific Docker image (`docker.redpanda.com/redpandadata/redpanda:-fips`) for `amd64` and `arm64` architectures, with the required OpenSSL FIPS module pre-configured. - -NOTE: If you are upgrading with FIPS mode enabled, ensure all SASL/SCRAM user passwords are at least 14 characters before upgrading. FIPS 140-3 enforces stricter HMAC key size requirements. - -See xref:manage:security/fips-compliance.adoc[] for configuration details. - -== Iceberg: Expanded JSON Schema support - -Redpanda now supports additional JSON Schema patterns when translating to Iceberg tables: - -* `$ref` support: Internal references using `$ref` (for example, `"$ref": "#/definitions/myType"`) are resolved from schema resources declared in the same document. External references are not yet supported. -* Map type from `additionalProperties`: `additionalProperties` objects that contain subschemas now translate to Iceberg `map`. -* `oneOf` nullable pattern: The `oneOf` keyword is now supported for the standard nullable pattern if exactly one branch is `{"type":"null"}` and the other is a non-null schema. - -See xref:manage:iceberg/specify-iceberg-schema.adoc#how-iceberg-modes-translate-to-table-format[Specify Iceberg Schema] for JSON types mapping and updated requirements. - -== Ordered rack preference for Leader Pinning - -xref:develop:produce-data/leader-pinning.adoc[Leader Pinning] now supports the `ordered_racks` configuration value, which lets you specify preferred racks in priority order. Unlike `racks`, which distributes leaders uniformly across all listed racks, `ordered_racks` places leaders in the highest-priority available rack and fails over to subsequent racks only when higher-priority racks become unavailable. - -== User-based throughput quotas - -Redpanda now supports throughput quotas based on authenticated user principals. Unlike client-based quotas (which rely on self-declared `client-id` values), user-based quotas enforce limits using verified identities from SASL, mTLS, or OIDC authentication. - -You can set quotas for individual users, default users, or fine-grained user/client combinations. See xref:manage:cluster-maintenance/about-throughput-quotas.adoc[] for conceptual details, and xref:manage:cluster-maintenance/manage-throughput.adoc#set-user-based-quotas[Set user-based quotas] to get started. - -== Cross-region Remote Read Replicas - -Remote Read Replica topics on AWS can be deployed in a different region from the origin cluster's S3 bucket. This enables cross-region disaster recovery and data locality scenarios while maintaining the read-only replication model. - -To create cross-region Remote Read Replica topics, configure dynamic upstreams that point to the origin cluster's S3 bucket location. Redpanda manages the number of concurrent dynamic upstreams based on your `cloud_storage_url_style` setting (virtual_host or path style). - -See xref:manage:tiered-storage.adoc#remote-read-replicas[Remote Read Replicas] for setup instructions and configuration details. - -== Automatic broker decommissioning - -When continuous partition balancing is enabled, Redpanda can automatically decommission brokers that remain unavailable for a configured duration. The xref:reference:properties/cluster-properties.adoc#partition_autobalancing_node_autodecommission_timeout_sec[`partition_autobalancing_node_autodecommission_timeout_sec`] property triggers permanent broker removal, unlike xref:reference:properties/cluster-properties.adoc#partition_autobalancing_node_availability_timeout_sec[`partition_autobalancing_node_availability_timeout_sec`] which only moves partitions temporarily. - -Key characteristics: - -* Disabled by default -* Requires `partition_autobalancing_mode` set to `continuous` -* Permanently removes the node from the cluster (the node cannot rejoin automatically) -* Processes one decommission at a time to maintain cluster stability -* Manual intervention required if decommission stalls - -See xref:manage:cluster-maintenance/continuous-data-balancing.adoc[] for configuration details. - -== Schema Registry contexts - -xref:manage:schema-reg/schema-reg-contexts.adoc[Schema Registry contexts] are namespaces that isolate schemas, subjects, and configurations within a single Schema Registry instance. Each context maintains its own schema ID counter, mode settings, and compatibility settings, so teams can share a Schema Registry without risking naming collisions or configuration drift. - -To enable contexts, set xref:reference:properties/cluster-properties.adoc#schema_registry_enable_qualified_subjects[`schema_registry_enable_qualified_subjects`] to `true` and restart your brokers. Once enabled, you reference schemas using qualified subject syntax, for example `:.staging:my-topic-value`. See xref:manage:schema-reg/schema-reg-contexts.adoc[] for configuration examples and limitations. - -== Schema Registry metadata properties - -xref:manage:schema-reg/schema-reg-overview.adoc#metadata-properties[Schema Registry metadata properties] let you store and retrieve arbitrary key-value pairs alongside schemas. Properties such as `owner`, `team`, or `application.version` travel with the schema through its lifecycle, making it easier to track ownership and lineage without modifying the schema itself. - -You can set metadata when registering a schema using the `POST /subjects/\{subject\}/versions` endpoint or with the xref:reference:rpk/rpk-registry/rpk-registry-schema-create.adoc[`--metadata-properties`] flag in `rpk registry schema create`. Metadata is returned in `GET /subjects/\{subject\}/versions/\{version\}` and `GET /schemas/ids/\{id\}` responses, and viewable with `rpk registry schema get --print-metadata`. New schema versions automatically inherit metadata from the most recent version of the subject unless you register with an explicit empty `metadata` object. - -== OIDC authentication with rpk - -Starting in v26.1.7, `rpk` supports the `OAUTHBEARER` SASL mechanism, so you can authenticate `rpk` to the Kafka API with an OIDC access token issued by your identity provider (IdP) instead of a SASL/SCRAM username and password. Pass the token through xref:reference:rpk/rpk-x-options.adoc#sasl-mechanism[`-X sasl.mechanism=OAUTHBEARER`] and xref:reference:rpk/rpk-x-options.adoc#pass[`-X pass="token:"`]. - -For end-to-end steps and prerequisites, see xref:manage:security/authentication.adoc#oidc-rpk[Connect to Redpanda with OIDC using rpk]. - -== New configuration properties - -**Storage mode:** - -* xref:reference:properties/cluster-properties.adoc#default_redpanda_storage_mode[`default_redpanda_storage_mode`]: Set the default storage mode for new topics (`local`, `tiered`, `cloud`, or `unset`) -* xref:reference:properties/topic-properties.adoc#redpanda-storage-mode[`redpanda.storage.mode`]: Set the storage mode for an individual topic, superseding the legacy `redpanda.remote.read` and `redpanda.remote.write` properties - -**Cloud Topics:** - -NOTE: Cloud Topics requires an Enterprise license. For more information, contact https://redpanda.com/try-redpanda?section=enterprise[Redpanda sales^]. - -* xref:reference:properties/cluster-properties.adoc#cloud_topics_allow_materialization_failure[`cloud_topics_allow_materialization_failure`]: Enable recovery from missing L0 extent objects -* xref:reference:properties/cluster-properties.adoc#cloud_topics_compaction_interval_ms[`cloud_topics_compaction_interval_ms`]: Interval for background compaction -* xref:reference:properties/cluster-properties.adoc#cloud_topics_compaction_key_map_memory[`cloud_topics_compaction_key_map_memory`]: Maximum memory per shard for compaction key-offset maps -* xref:reference:properties/cluster-properties.adoc#cloud_topics_compaction_max_object_size[`cloud_topics_compaction_max_object_size`]: Maximum size for L1 objects produced by compaction -* xref:reference:properties/cluster-properties.adoc#cloud_topics_epoch_service_max_same_epoch_duration[`cloud_topics_epoch_service_max_same_epoch_duration`]: Maximum duration a node can use the same epoch -* xref:reference:properties/cluster-properties.adoc#cloud_topics_fetch_debounce_enabled[`cloud_topics_fetch_debounce_enabled`]: Enable fetch debouncing -* xref:reference:properties/cluster-properties.adoc#cloud_topics_gc_health_check_interval[`cloud_topics_gc_health_check_interval`]: L0 garbage collector health check interval -* xref:reference:properties/cluster-properties.adoc#cloud_topics_l1_indexing_interval[`cloud_topics_l1_indexing_interval`]: Byte interval for index entries in long-term storage objects -* xref:reference:properties/cluster-properties.adoc#cloud_topics_long_term_file_deletion_delay[`cloud_topics_long_term_file_deletion_delay`]: Delay before deleting stale long-term files -* xref:reference:properties/cluster-properties.adoc#cloud_topics_long_term_flush_interval[`cloud_topics_long_term_flush_interval`]: Interval for flushing long-term storage metadata to object storage -* xref:reference:properties/cluster-properties.adoc#cloud_topics_metastore_lsm_apply_timeout_ms[`cloud_topics_metastore_lsm_apply_timeout_ms`]: Timeout for applying replicated writes to LSM database -* xref:reference:properties/cluster-properties.adoc#cloud_topics_metastore_replication_timeout_ms[`cloud_topics_metastore_replication_timeout_ms`]: Timeout for L1 metastore Raft replication -* xref:reference:properties/cluster-properties.adoc#cloud_topics_num_metastore_partitions[`cloud_topics_num_metastore_partitions`]: Number of partitions for the metastore topic -* xref:reference:properties/cluster-properties.adoc#cloud_topics_parallel_fetch_enabled[`cloud_topics_parallel_fetch_enabled`]: Enable parallel fetching -* xref:reference:properties/cluster-properties.adoc#cloud_topics_preregistered_object_ttl[`cloud_topics_preregistered_object_ttl`]: Time-to-live for pre-registered L1 objects -* xref:reference:properties/cluster-properties.adoc#cloud_topics_produce_no_pid_concurrency[`cloud_topics_produce_no_pid_concurrency`]: Concurrent Raft requests for producers without a producer ID -* xref:reference:properties/cluster-properties.adoc#cloud_topics_produce_write_inflight_limit[`cloud_topics_produce_write_inflight_limit`]: Maximum in-flight write requests per shard -* xref:reference:properties/cluster-properties.adoc#cloud_topics_reconciliation_max_interval[`cloud_topics_reconciliation_max_interval`]: Maximum reconciliation interval for adaptive scheduling -* xref:reference:properties/cluster-properties.adoc#cloud_topics_reconciliation_max_object_size[`cloud_topics_reconciliation_max_object_size`]: Maximum size for L1 objects produced by the reconciler -* xref:reference:properties/cluster-properties.adoc#cloud_topics_reconciliation_min_interval[`cloud_topics_reconciliation_min_interval`]: Minimum reconciliation interval for adaptive scheduling -* xref:reference:properties/cluster-properties.adoc#cloud_topics_reconciliation_parallelism[`cloud_topics_reconciliation_parallelism`]: Maximum concurrent objects built by reconciliation per shard -* xref:reference:properties/cluster-properties.adoc#cloud_topics_reconciliation_slowdown_blend[`cloud_topics_reconciliation_slowdown_blend`]: Blend factor for slowing down reconciliation -* xref:reference:properties/cluster-properties.adoc#cloud_topics_reconciliation_speedup_blend[`cloud_topics_reconciliation_speedup_blend`]: Blend factor for speeding up reconciliation -* xref:reference:properties/cluster-properties.adoc#cloud_topics_reconciliation_target_fill_ratio[`cloud_topics_reconciliation_target_fill_ratio`]: Target fill ratio for L1 objects -* xref:reference:properties/cluster-properties.adoc#cloud_topics_upload_part_size[`cloud_topics_upload_part_size`]: Part size for multipart uploads -* xref:reference:properties/cluster-properties.adoc#cloud_topics_epoch_service_epoch_increment_interval[`cloud_topics_epoch_service_epoch_increment_interval`]: Interval for cluster epoch incrementation -* xref:reference:properties/cluster-properties.adoc#cloud_topics_epoch_service_local_epoch_cache_duration[`cloud_topics_epoch_service_local_epoch_cache_duration`]: Cache duration for local epoch data -* xref:reference:properties/cluster-properties.adoc#cloud_topics_long_term_garbage_collection_interval[`cloud_topics_long_term_garbage_collection_interval`]: Interval for long-term storage garbage collection -* xref:reference:properties/cluster-properties.adoc#cloud_topics_produce_batching_size_threshold[`cloud_topics_produce_batching_size_threshold`]: Object size threshold that triggers upload -* xref:reference:properties/cluster-properties.adoc#cloud_topics_produce_cardinality_threshold[`cloud_topics_produce_cardinality_threshold`]: Partition cardinality threshold that triggers upload -* xref:reference:properties/cluster-properties.adoc#cloud_topics_produce_upload_interval[`cloud_topics_produce_upload_interval`]: Time interval that triggers upload -* xref:reference:properties/cluster-properties.adoc#cloud_topics_reconciliation_interval[`cloud_topics_reconciliation_interval`]: Interval for moving data from short-term to long-term storage -* xref:reference:properties/cluster-properties.adoc#cloud_topics_short_term_gc_backoff_interval[`cloud_topics_short_term_gc_backoff_interval`]: Backoff interval for short-term storage garbage collection -* xref:reference:properties/cluster-properties.adoc#cloud_topics_short_term_gc_interval[`cloud_topics_short_term_gc_interval`]: Interval for short-term storage garbage collection -* xref:reference:properties/cluster-properties.adoc#cloud_topics_short_term_gc_minimum_object_age[`cloud_topics_short_term_gc_minimum_object_age`]: Minimum age for objects to be eligible for short-term garbage collection - -**Object storage:** - -* xref:reference:properties/object-storage-properties.adoc#cloud_storage_gc_max_segments_per_run[`cloud_storage_gc_max_segments_per_run`]: Maximum number of log segments to delete from object storage during each xref:manage:tiered-storage.adoc#object-storage-housekeeping[housekeeping run] -* xref:reference:properties/object-storage-properties.adoc#cloud_storage_prefetch_segments_max[`cloud_storage_prefetch_segments_max`]: Maximum number of small segments to prefetch during sequential reads - -**Authentication:** - -* xref:reference:properties/cluster-properties.adoc#nested_group_behavior[`nested_group_behavior`]: Control how Redpanda handles nested groups extracted from authentication tokens -* xref:reference:properties/cluster-properties.adoc#oidc_group_claim_path[`oidc_group_claim_path`]: JSON path to extract groups from the JWT payload -* xref:reference:properties/cluster-properties.adoc#schema_registry_enable_qualified_subjects[`schema_registry_enable_qualified_subjects`]: Enable parsing of qualified subject syntax in Schema Registry - -**Other:** - -* xref:reference:properties/cluster-properties.adoc#delete_topic_enable[`delete_topic_enable`]: Enable or disable topic deletion via the Kafka DeleteTopics API -* xref:reference:properties/cluster-properties.adoc#internal_rpc_request_timeout_ms[`internal_rpc_request_timeout_ms`]: Default timeout for internal RPC requests between nodes -* xref:reference:properties/cluster-properties.adoc#log_compaction_max_priority_wait_ms[`log_compaction_max_priority_wait_ms`]: Maximum time a priority partition (such as `__consumer_offsets`) waits before preempting regular compaction -* xref:reference:properties/cluster-properties.adoc#partition_autobalancing_node_autodecommission_timeout_sec[`partition_autobalancing_node_autodecommission_timeout_sec`]: Duration a node must be unavailable before Redpanda automatically decommissions it - -=== Changes to default values - -* xref:reference:properties/cluster-properties.adoc#log_compaction_tx_batch_removal_enabled[`log_compaction_tx_batch_removal_enabled`]: Changed from `false` to `true`. -* xref:reference:properties/cluster-properties.adoc#tls_v1_2_cipher_suites[`tls_v1_2_cipher_suites`]: Changed from OpenSSL cipher names to IANA cipher names. - -==== v26.1.4 - -* xref:reference:properties/cluster-properties.adoc#max_concurrent_producer_ids[`max_concurrent_producer_ids`]: Changed from unlimited to `100000` to prevent unbounded memory growth with heavy producer usage. - -* xref:reference:properties/cluster-properties.adoc#max_transactions_per_coordinator[`max_transactions_per_coordinator`]: Changed from unlimited to `10000` to prevent resource exhaustion from excessive transaction sessions. - -=== Removed properties - -The following deprecated configuration properties have been removed in v26.1.1. If you have any of these in your configuration files, update them according to the guidance below. - -**RPC timeout properties:** - -Replace with xref:reference:properties/cluster-properties.adoc#internal_rpc_request_timeout_ms[`internal_rpc_request_timeout_ms`]. - -* `alter_topic_cfg_timeout_ms` -* `create_topic_timeout_ms` -* `metadata_status_wait_timeout_ms` -* `node_management_operation_timeout_ms` -* `recovery_append_timeout_ms` -* `rm_sync_timeout_ms` -* `tm_sync_timeout_ms` -* `wait_for_leader_timeout_ms` - -**Client throughput quota properties:** - -Use xref:reference:rpk/rpk-cluster/rpk-cluster-quotas.adoc[`rpk cluster quotas`] to manage xref:manage:cluster-maintenance/manage-throughput.adoc#client-throughput-limits[client throughput limits]. - -* `kafka_admin_topic_api_rate` -* `kafka_client_group_byte_rate_quota` -* `kafka_client_group_fetch_byte_rate_quota` -* `target_fetch_quota_byte_rate` -* `target_quota_byte_rate` - -**Quota balancer properties:** - -Use xref:manage:cluster-maintenance/manage-throughput.adoc#broker-wide-throughput-limit-properties[broker-wide throughput limit properties]. - -* `kafka_quota_balancer_min_shard_throughput_bps` -* `kafka_quota_balancer_min_shard_throughput_ratio` -* `kafka_quota_balancer_node_period` -* `kafka_quota_balancer_window` -* `kafka_throughput_throttling_v2` - -**Timestamp alert properties:** - -* `log_message_timestamp_alert_after_ms`: Use xref:reference:properties/cluster-properties.adoc#log_message_timestamp_after_max_ms[`log_message_timestamp_after_max_ms`] -* `log_message_timestamp_alert_before_ms`: Use xref:reference:properties/cluster-properties.adoc#log_message_timestamp_before_max_ms[`log_message_timestamp_before_max_ms`] - -**Other removed properties:** - -No replacement needed. These properties were deprecated placeholders that have been silently ignored and will continue to be ignored even after removal. - -* `cloud_storage_disable_metadata_consistency_checks` -* `cloud_storage_reconciliation_ms` -* `coproc_max_batch_size` -* `coproc_max_inflight_bytes` -* `coproc_max_ingest_bytes` -* `coproc_offset_flush_interval_ms` -* `datalake_disk_space_monitor_interval` -* `enable_admin_api` -* `enable_coproc` -* `find_coordinator_timeout_ms` -* `full_raft_configuration_recovery_pattern` -* `id_allocator_replication` -* `kafka_memory_batch_size_estimate_for_fetch` -* `log_compaction_adjacent_merge_self_compaction_count` -* `max_version` -* `min_version` -* `raft_max_concurrent_append_requests_per_follower` -* `raft_recovery_default_read_size` -* `rm_violation_recovery_policy` -* `schema_registry_protobuf_renderer_v2` -* `seed_server_meta_topic_partitions` -* `seq_table_min_size` -* `tm_violation_recovery_policy` -* `transaction_coordinator_replication` -* `tx_registry_log_capacity` -* `tx_registry_sync_timeout_ms` -* `use_scheduling_groups` +See xref:develop:kafka-clients.adoc[Kafka Compatibility] for the full list of validated clients and known exceptions.