Amazon EKS (Kafka)
General steps: update Kafka's
advertised.listenersand make sure Kafka is accessible (e.g. allow inputs on Security Groups).
You will probably face the following problems.
If you want to connect to Kafka outside of EKS, you will need to change
advertised.listeners. When a client connects to a single Kafka bootstrap server (like other brokers), a bootstrap server sends a list of addresses for all brokers to the client. If you want to connect to a EKS Kafka, these default values will not be correct. This post provides an excellent explanation of the field.
helm upgradeon the Kafka chart does not always update the pods. The exact reason is unknown. It's probably an issue with the chart's implementation. You should run
kubectl describe podand other commands to see the current status of the pods. During initial development, you can run
helm uninstalland then
helm installto force the values to update.