Mismatch kafka bootstrapURL after kafka broker scale up

[totochichi]

Hello everyone,

When I try to scale up the existing cluster, we have kafka broker's bootstrapURL mis-aligned with actual broker id.
When we scaled up from 3 to 6 brokers, new broker ID will start from 6, 7 ,8 , as Kafka controllers takes up 3-5. However the host list is iterated from 0 to # of replicas ( This is our initial set up without utilizing NodePoolIDs and we have a couple of clusters running), so bootstrap URL is generated for broker 0, 1, 2, 3, 4, 5 instead of 0, 1, 2, 6, 7, 8.

{{- range $i, $e := until (.Values.kafka.broker.replicas|int) }} - host: broker{{$i}}.kafka.{{ $.Values.subDomain }}.{{ $.Values.phzZone }}

Leveraging Node Pool ID will work well for net new clusters, but not for existing clusters. Is there a way to get bootstrapURL dynamically updated as we scaled up kafka brokers?

[scholzj]

You should probably provide more details on what exactly you are doing and what you are talking about, etc. E.g., what is that code you shared and where does it come from, how does your configuration look like, etc.

In general, you should always use the bootstrap address provided in the .status section of the Kafka CR