Embedded Hazelcast Server and TCPIP based discovery in Kubernetes Cluster possible or not?

[Rakesh Sharma]

Is it possible to use the TCPIP based discovery in Kubernetes cluster without using kubernetes adapter? 

We have StateFulSet for Embedded EidgServer and then We have HeadLess Service configured for it. 

Since we have StateFulSet for our EmbeddedHazelcast Server we get predicted hostnames--eidgserve1-0, eidgserver1-1 and so on. I was hoping they should be able to form cluster using TCPIP based discovery. But each pod is forming it's own cluster. 

Same code works fine in NON Kubernetes environment.

Thanks,

Rakesh Sharma

[Neil Stevenson]

Based on your description, I think that "eidgserve1-0," and "eidgserve1-1" are pod names not host names. You could prove this by connecting to pod and trying to ping one of the others by name.

How would using TCP-IP discovery be preferable in Kubernetes to using the Kubernetes discovery ?

It might be possible, especially with the IP addresses, I'm just trying to understand what the point would be

Neil

[Rakesh Sharma]

I was able to fix the issue related to DNS in my StatefulSet resource using dnsConfig and added a search with

<service-name>.<namespace>.svc.cluster.local

That solved the issue resolving pods short host name on Kubernetes cluster.

Rakesh

This message contains confidential information and is intended only for the individuals named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required, please request a hard-copy version. -Hazelcast

--
You received this message because you are subscribed to a topic in the Google Groups "Hazelcast" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/hazelcast/hLj6xFOno9o/unsubscribe.
To unsubscribe from this group and all its topics, send an email to hazelcast+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hazelcast/3df90d24-ab3e-440d-bc6f-694bb69057e6n%40googlegroups.com.