KIP-1242 — Detection and handling of misrouted connections

Accepted BrokerProtocol

Introduces misrouted-connection detection by having the broker send a DisconnectResponse (or equivalent signal) when a client connects to the wrong broker, enabling the client to refresh metadata and reconnect correctly. In Kubernetes rolling restarts, a broker can change its advertised hostname and a client using stale bootstrap metadata silently connects to the wrong broker, leading to confusing failures that require a full client restart to resolve.

Details