-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Description
Name and Version
bitnami/kafka
What steps will reproduce the bug?
Hi Team,
We are currently migrating Kafka to KRaft, and as part of this, we upgraded our Bitnami Kafka chart from version 20.0.7 to 24.0.7.
In version 24.0.7, we are facing an issue where the init container is trying to use a different LoadBalancer service that is not part of our Helm chart.
Our existing Kafka external LoadBalancer services (used for external access) are:
- kafka-pre-kraft-qa3-0-external
- kafka-pre-kraft-qa3-1-external
- kafka-pre-kraft-qa3-2-external
But in the init container logs, we see errors like:
"Error from server (NotFound): services "kafka-pre-kraft-qa3-broker-2-external" not found"
The init container is expecting a service named kafka-pre-kraft-qa3-broker-2-external, which does not exist.
How can I configure the chart so that the init container uses our existing LoadBalancer services? I tried a few values from the Helm chart documentation, but nothing worked as expected.
I am attaching my Helm chart values as well. Please help.
helm upgrade kafka-pre-kraft-qa3 -f values.yml bitnami/kafka --version 24.0.7
broker:
replicaCount: 3
sasl:
enabledMechanisms: PLAIN
client:
users:
- XXXXXXXXXXXX
- XXXXXXXXXXXX
- XXXXXXXXXXXX
passwords:
- XXXXXXXXXXXXXXXXXXXX
- XXXXXXXXXXXXXXXXXXXX
- XXXXXXXXXXXXXXXXXXXX
listeners:
client:
client:
protocol: SASL_SSL
tls:
type: JKS
existingSecret:
- XXXXXXXXXXXXXX
- XXXXXXXXXXXXXX
- XXXXXXXXXXXXXX
password: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
externalAccess:
enabled: true
autoDiscovery:
enabled: true
service:
broker:
type: LoadBalancer
ports:
external: 9094
rbac:
create: true
serviceAccount:
create: true
zookeeper:
enabled: true
kraft:
enabled: false
controller:
replicaCount: 0What do you see instead?
Not able to change the external host for init containers