We see some annoying behavior with S3 discovery because Ignite will push to the discovery S3 bucket the IP address of the local docker bridge network (172.17.0.1) in our case. Basically, each node when coming online tries that address first, and has to go through a network timeout to recover.
To address this, have prototyped a simple extension to TcpCommunicationSpi to allow configuration of a list of IP addresses that should be completely ignored, and will create a ticket and generate a pull request for it. If there is a better approach, please let us know. Thanks Dave Harvey
