Loading…
Topic
JBoss EAP
1 post about JBoss EAP. Every summary links to the original.
- 1 post
- 1 company
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
Posts
JBoss EAP clustering in OpenShift: KUBE_PING discovery
This article explores the JGroups KUBE_PING discovery protocol for clustering JBoss EAP 7 and JBoss EAP 8 in Red Hat OpenShift 4. KUBE_PING queries the Kubernetes API directly for pod IP addresses, then filters them by namespace and labels to establish peer-to-peer TCP connections. Configuring KUBE_PING requires setting three environment variables: JGROUPS_PING_PROTOCOL, KUBERNETES_NAMESPACE, and KUBERNETES_LABELS. The default service account must be granted the view role on the namespace to avoid HTTP 403 errors. In JBoss EAP 8, clustering is not enabled by default and must be provisioned via Galleon layers during the build process.
Related topics
All topics →Weekly digest
The best engineering reads, once a week.