Open jerrinot opened 3 years ago
@jerrinot, makes sense, giving starting point to user would provide more smoother process.
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.
This is how my cluster looks like:
I have 3 pods with Hazelcast running, each pod has a load balancer assigned. However I also have an unrelated deployment with NFS PV provisioner. The cluster is running fine, but a client fails to translate discovered PODs to public addresses because of this check
Perhaps it's OK to be conservative and skip the translation altogether. But it would be really helpful to print a hint - what's going on. Something like "I found public IP of 3 PODs, but failed to resolve this and that. It's possible the POD is not from Hazelcast and you should do this"