You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support for kafka rack awareness was added in #13308, but dropped in #17507. I believe this was unintentional since I cannot find anything mentioning this in the commit message.
The property broker.rack is not a property that can simply be filled via extraConfig because it requires a dynamic value setting, that depends on the availability zone where the pod is scheduled.
Are you using any custom parameters or values?
No response
What is the expected behavior?
Can you add support for this unintentional removal of functionality.
The previous bitnami/kafka chart version that we used supporting this functionality was 22.0.1
What do you see instead?
No support via any of the chart parameters.
Additional information
No response
The text was updated successfully, but these errors were encountered:
rubenvw-ngdata
changed the title
Migration to Kafka 3.5 dropped support for rack awareness
[bitnami/kafka] Migration to Kafka 3.5 dropped support for rack awareness
May 8, 2024
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.
Name and Version
bitnami/kafka 28.1.1
What architecture are you using?
None
What steps will reproduce the bug?
Support for kafka rack awareness was added in #13308, but dropped in #17507. I believe this was unintentional since I cannot find anything mentioning this in the commit message.
The property
broker.rack
is not a property that can simply be filled viaextraConfig
because it requires a dynamic value setting, that depends on the availability zone where the pod is scheduled.Are you using any custom parameters or values?
No response
What is the expected behavior?
Can you add support for this unintentional removal of functionality.
The previous bitnami/kafka chart version that we used supporting this functionality was 22.0.1
What do you see instead?
No support via any of the chart parameters.
Additional information
No response
The text was updated successfully, but these errors were encountered: