Issues with Payara Server Configuration in a Kubernetes Environment

General
1

Hey guys… :blush:

I have been working on setting up a Payara server in a Kubernetes environment, and I am running into some issues that I haven’t been able to resolve. I am using Payara Micro (v6.2023.1) and deploying my application on a cluster managed by AKS (Azure Kubernetes Service). While the basic setup works fine, I am facing problems with service discovery and load balancing between the different instances.

Here are the issues I have faced:

  1. Service Discovery: When I scale up the number of replicas, the new instances don’t seem to properly join the cluster. I’ve configured the --autoBindHttp and --clusterName options, but it looks like they aren’t able to communicate correctly. Is there something specific I need to do with Payara’s Hazelcast integration to ensure proper clustering?
  2. Load Balancing: While Kubernetes is handling the service’s external traffic, I’ve noticed some inconsistency in the load distribution across the Payara instances. It seems like some instances are getting more traffic than others, and I’m not sure why this imbalance is happening.

I also check this: https://forum.payara.fish/t/payara-server-and-ram-consumption-in-dockerized-environmenmendix But I have not found any solution. Could anyone guide me about this? If anyone has experience deploying Payara in Kubernetes and can point me in the right direction, I’d greatly appreciate it! Also, any advice on best practices for configuring Payara Micro in a cloud-native environment would be really helpful.

Thanks in advance for your help!

Respected community member! :innocent: