(kafka) branch trunk updated: MINOR: Add upgrade note for config provider allowlist on dynamic broker configs (#23480)

[ma...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

omkreddy pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/trunk by this push:
     new 13475a276ed MINOR: Add upgrade note for config provider allowlist on dynamic broker configs (#23480)
13475a276ed is described below

commit 13475a276edad03f98fa4313839a3d87aed46c6f
Author: Manikumar Reddy <ma...@gmail.com>
AuthorDate: Fri Sep 18 14:38:01 2026 +0530

    MINOR: Add upgrade note for config provider allowlist on dynamic broker configs (#23480)
---
 docs/getting-started/upgrade.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/getting-started/upgrade.md b/docs/getting-started/upgrade.md
index 7ddfc188112..6f29bf93550 100644
--- a/docs/getting-started/upgrade.md
+++ b/docs/getting-started/upgrade.md
@@ -56,6 +56,7 @@ type: docs
   * Controllers can now be unregistered from the cluster metadata. A new `kafka-cluster.sh unregister-controller` command and a `--unregister` flag on `kafka-metadata-quorum.sh remove-controller` are provided, backed by the new `Admin#unregisterController` API and the new `UnregisterController` RPC. This introduces the error code `CONTROLLER_ID_NOT_REGISTERED` (136) and requires metadata version `4.4-IV2` (`IBP_4_4_IV2`). For further details, please refer to [KIP-1312](https://cwiki.apac [...]
   * A new client configuration, `bootstrap.resolve.timeout.ms`, controls how DNS resolution of `bootstrap.servers` is performed. The default value of `0` preserves the historical synchronous behavior. Setting a positive value opts into asynchronous bootstrap resolution: the client constructor returns immediately, `NetworkClient` retries DNS resolution up to the configured timeout, and failures are surfaced later as `BootstrapResolutionExceptions` from subsequent API calls. This failure i [...]
   * For tiered-storage topics, time-based local retention (`local.retention.ms`) now uses a segment's last modified time as the age anchor when the segment's largest record timestamp is in the future. Previously such a segment was never removed by time-based retention (its future timestamp kept it perpetually within the retention window) and was only reclaimed once `local.retention.bytes` was breached, even though it had already been uploaded to remote storage. For further details, pleas [...]
+  * The `org.apache.kafka.automatic.config.providers` allowlist is now applied when dynamic broker configurations are validated and applied.
   * `group.consumer.assignors` now fails broker startup with a `ConfigException` when two configured assignors resolve to the same name, for example a built-in listed both by its name and by its class name, or a custom assignor reusing the name of another configured assignor. Such a configuration used to pass startup validation and fail later during group coordinator loading. For further details, please refer to [KAFKA-20843](https://issues.apache.org/jira/browse/KAFKA-20843).
 
 ## Upgrading to 4.3.1