@MarijeSchillern  I don't see  any setting like hazelcast/external/members in the links you provided below.

You mentioned "Here is an example". However I don't see any relevant attachments that shows this example. Can you provide the attachment? Also, the comment you provided was based on the assumption that hazelcast was deployed using the war file or is the sample relevant to pega clusters running externally(on VMs through VM Based deployment model) connecting to hazelcast running on EKS?

Here are my questions. Can you provide your response for the below?

1. We are trying to connect our pega nodes running outside of EKS(on VM – Elastic Beanstalk) to hazelcast service running on EKS.
2. The documentation supports connecting to the clustering service only via IP. We tried using the Load balancer IP(for the Service running on EKS) that is exposed for this connection and it didn’t work as expected.
3. I have attached the cluster logs and pega rules log to the ticket.
4. Earlier, we tried using the DNS(for the load balancer) to connect to the service and it didn’t work either
5. We want to know 1) If we can connect to the hazelcast/clustering service if the pega nodes are running outside of EKS  or whether it can be connected to only from within the K8S Cluster? 2) If we can use the DNS instead of IPs since DNS has a higher level of abstraction and we don’t have to worry about Pods getting replaced(in which case the IP will change) – This question is applicable for both (hybrid mode and also if both pega as well as the clustering service is running on the same cluster).