...

• For example, for 3.7.0 version of kafka, the image name with tagging would be apache/kafka:3.7.0
• In case of a CVE post 3.7.0, the name of the released image will depend on the section ReleaseProcess
  
  • apache/kafka:3.7.1 => Docker release along with Apache Kafka minor release
  • apache/kafka:3.7.0-1 => Only docker image release, hence added a suffix

Configuring Properties

We offer two methods for passing the above properties to the container:

1. File Mounting: Users can mount a properties file to a specific path within the container (we will clearly document this path). This file will then be utilized to start up Kafka.

2. Using Environment Variables: Alternatively, users have the option to provide configurations via environment variables. Here's how to structure these variables:

   • Replace . with _
   • Replace _ with __(double underscore)
   • Replace - with ___(triple underscore)
   • Prefix the result with KAFKA_

   Examples:

   • For abc.def, use KAFKA_ABC_DEF
   • For abc-def, use KAFKA_ABC___DEF
   • For abc_def, use KAFKA_ABC__DEF

This way, you have flexibility in how you pass configurations to the container, making it more adaptable to various user preferences and requirements.

NOTE: If a property is provided both in the mounted file and as an environment variable, the value from the environment variable will take precedence.

Compatibility, Deprecation, and Migration Plan

...