How to do hazelcast configuration for kubernetes cluster across node?

[Hariharan Palani]

Hi,

   We are developing microservice application using vertx 3.6. We are deploying the application using kubernetes.

For hazelcast, we use hazelcast-kubernetes package and configuration based on explanation given in the below link,

https://vertx.io/docs/vertx-hazelcast/java/#_configuring_for_kubernetes

After deployment, hazelcast is working fine and can able to find all the members in a node. But it fails to find the members 

available in another node in the kubernetes cluster.

Can you please help to resolve this issue? It is very urgent for us.

Following is the headless service created for hazelcast,

apiVersion: v1

kind: Service

metadata:

 name: cb-hazelcast-service

spec:

 selector:

   component: cb-hazelcast-service

 clusterIP: None

 ports:

 - name: hz-port-name

   port: 5701

   protocol: TCP

we attached the component label in all the deployment for microservices and our hazelcast configuration looks as follows,

<?xml version="1.0" encoding="UTF-8"?>

<hazelcast xsi:schemaLocation="http://www.hazelcast.com/schema/config hazelcast-config-3.6.xsd"

xmlns="http://www.hazelcast.com/schema/config"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<properties>

<property name="hazelcast.discovery.enabled">true</property>

<property name="hazelcast.rest.enabled">false</property>

</properties>

<network>

<port auto-increment="true" port-count="10000">5701</port>

<outbound-ports>

<ports>0</ports>

</outbound-ports>

<join>

<multicast enabled="false"/>

<tcp-ip enabled="false"/>

<discovery-strategies>

<discovery-strategy enabled="true"

class="com.hazelcast.kubernetes.HazelcastKubernetesDiscoveryStrategy">

<properties>

<property name="service-dns">cb-hazelcast-service</property>

</properties>

</discovery-strategy>

</discovery-strategies>

</join>

</network> 

</hazelcast>

please let me know if any additional information required.

[Thomas SEGISMONT]

Can you verify your service-dns? Usually it's in the form MY-SERVICE-NAME.MY-NAMESPACE.svc.cluster.local

--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/43a87a65-2c81-4772-804d-b05fad92b7d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Hariharan Palani]

It is not working even after updating the dns name in the form MY-SERVICE-NAME.MY-NAMESPACE.svc.cluster.local

To unsubscribe from this group and stop receiving emails from it, send an email to ve...@googlegroups.com.

[Thomas SEGISMONT]

Then can you verify network policy? Someone reported recently it was a blocker: https://github.com/vert-x3/vertx-hazelcast/issues/113#issuecomment-479707186

Then I would also suggest to ping the Hazelcast folks on their user group.

To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.

Visit this group at https://groups.google.com/group/vertx.

To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/2dbd2ed9-10af-4067-af5f-579bc4d06a8b%40googlegroups.com.