[bitnami/kafka] Migration to Kafka 3.5 dropped support for rack awareness about charts HOT 2 CLOSED

As @rubenvw-ngdata says, this was dropped in #17507. To be even more specific, here: https://github.com/bitnami/charts/pull/17507/files#r1594006644

from charts.

Hi there, as mentioned, the value brokerRackAssignment was removed during the Kafka chart major refactor.

During the chart major, we introduced several changes, such as better support for KRaft architecture, improved security standards with the introduction of the readOnlyRootFilesystem=true, as well as change how the deployment is configure, relying on mounted configuration and init container logic instead of container-specific configurations.

In addition to those changes, we removed many custom values in favor of the general common values, such as extraEnvVars, extraInitContainers, extraConfig, etc.

I may have accidentally removed this value, I didn't notice it relied on running curl in runtime, therefore it could not be replaced by extraConfig.

I have submitted #26296 restoring the missing feature, sorry for the inconvenience.

from charts.