title: 'partitions have leader brokers without a matching listener' on kubernetes after kafka restart
body: <p>i have several spring boot apps communicating via kafka running inside a kubernetes cluster. Using the bitnami/kafka helm chart for deploying kafka.</p>
  
  <p>Everything works fine until the kafka broker (i only have a single instance) is restarting. After that i get for producer 'X partitions have leader brokers without a matching listener' ... to fix that i must setup the whole cluster again to make it working means kill all apps, remove kafka and the volumes and put everything back.</p>
  
  <p>Found some stuff regarding "advertised.listeners" but nothing worked yet.
  For example that one:
  <a href="https://medium.com/@tsuyoshiushio/configuring-kafka-on-kubernetes-makes-available-from-an-external-client-with-helm-96e9308ee9f4" rel="nofollow noreferrer">https://medium.com/@tsuyoshiushio/configuring-kafka-on-kubernetes-makes-available-from-an-external-client-with-helm-96e9308ee9f4</a></p>
  
  <p>The question for me is, why is it working in the beginning and only after crashing it stops .... </p>
  
  <p>Thx
  Oliver</p>