Rafał Leszko

@abx-firez As mentioned earlier, please attach the reproducer without Vertx, just Hazelcast. Then, I'll try to have a look.

This issue is probably related to Hazelcast itself, not Kubernetes plugin, because we see it in some other scenarios, like this https://github.com/hazelcast/hazelcast/issues/15446 I was not able to reproduce it with...

> @leszko > Can this problem be related to situation when hazelcast embedded in application and its container expose two ports, one for http (tomcat) and second for hazelcast? >...

It's hard to tell where Hazelcast tries to connect to. Some more questions: 1. If you follow exactly the code in [this guide](https://guides.hazelcast.org/kubernetes-embedded/), do you experience the same? 2. If...

It may be the [phone home](https://docs.hazelcast.com/imdg/4.2/phone-homes.html) call. Could you try disabling phone home and check if it helps?

So you'd like to have one Hazelcast cluster stretched across multiple Kubernetes clusters, right? Technically, you could do it by using host network or host port (but it's not a...

Yeah, agree. I think the behavior is correct because you have somehow misconfigured the Hazelcast cluster. But yeah, we could give some info to the user.

You should not set up one Hazelcast cluster across multiple Kubernetes clusters. Use WAN replication instead. Here's a related Hazelcast Guide: https://guides.hazelcast.org/kubernetes-wan/

@Franck-UltimaRatio @stronk-dev Can you confirm that is still an issue?

Is there any way you can check the Brodcaster's ETH addresses these request are coming from?