AMQ Streams doesn't refresh DNS addresses

Issue

• When recycling the AMQ Streams pods, the client applications maintains the IP address of the killed pods.
• Client application tries to connect to the old IP address with the following WARN message in the logs:

WARN [Producer clientId=console-producer] Connection to node 0 (my-cluster-kafka-0.my-cluster-kafka-brokers.myproject.svc.cluster.local/192.168.0.x:9092) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
WARN [Consumer clientId=consumer-1, groupId=console-consumer-997] Connection to node 0 (my-cluster-kafka-0.my-cluster-kafka-brokers.myproject.svc.cluster.local/192.168.0.x:9092) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)