mirror of
https://github.com/bitnami/containers.git
synced 2026-03-06 06:58:01 +08:00
[bitnami/kafka] Issue 77101 Fix Typo and Improve Clarity in Documentation (#77132)
This commit is contained in:
@@ -940,8 +940,9 @@ This new release of the bitnami/kafka container includes a refactor in its logic
|
||||
New variables have been added for this purpose:
|
||||
* KAFKA_CONTROLLER_USER - Username for the controller communications when SASL is enabled.
|
||||
* KAFKA_CONTROLLER_PASSWORD - Password for the controller communications when SASL is enabled.
|
||||
* Removed the `"${KAFKA_CONFIG}/server.properties"` vs `${KAFKA_CONFIG}/kraft/server.properties` when using Zookeeper of KRaft mode.
|
||||
By default, Kafka will use `"${KAFKA_CONFIG}/server.properties"`, but the base file has been modified at build time to remove references to both modes.
|
||||
* Removed the `${KAFKA_CONFIG}/server.properties` vs `${KAFKA_CONFIG}/kraft/server.properties` when using Zookeeper or KRaft mode.
|
||||
By default, Kafka will use `${KAFKA_CONFIG}/server.properties` which is generated by `${KAFKA_CONFIG}/server.properties.original` based on environment variables.
|
||||
And the base file `${KAFKA_CONFIG}/server.properties.original` is the original Kafka configuration file. If no custom configuration file is mounted, references to both modes will be removed during container initialization.
|
||||
* Refactor JAAS settings to use the recommended approach `listener.name.${listener_lower}.${mechanism_name}.sasl.jaas.config`.
|
||||
The `kafka_jaas.conf` will no longer be generated, although it will continue being loaded if mounted.
|
||||
Please note that, according to Kafka documentation, the preference will be:
|
||||
|
||||
Reference in New Issue
Block a user