---
title: "JBoss EAP"
description: "1 posts about JBoss EAP, summarised, each linking to the original."
---

# JBoss EAP
> 1 posts about JBoss EAP, summarised, each linking to the original.

## Articles

### [JBoss EAP clustering in OpenShift: KUBE\_PING discovery](https://yomu.fyi/post/jboss-eap-clustering-in-openshift-kube-ping-discovery.md)
- Company: [Red Hat](https://yomu.fyi/company/red-hat.md)
- Author: Francisco De Melo Junior, Alexander Barbosa Ayala
- Published: Nov 3, 2026
- Type: Tutorial

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.
