---
title: "JBoss EAP clustering in OpenShift: KUBE_PING discovery"
description: "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."
---

# JBoss EAP clustering in OpenShift: KUBE\_PING discovery

[Red Hat](https://yomu.fyi/company/red-hat) · Francisco De Melo Junior, Alexander Barbosa Ayala · Nov 3, 2026

**Type:** Tutorial

## Summary

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.

## Context

This article is part 2 of a series on clustering JBoss EAP 7 and JBoss EAP 8 in Red Hat OpenShift 4. It focuses on the KUBE\_PING discovery protocol, which queries the Kubernetes API directly for pod IP addresses, as an alternative to DNS\_PING covered in part 1.

## Approach / What changed

Configure the JGroups KUBE\_PING protocol by setting three environment variables (JGROUPS\_PING\_PROTOCOL to kubernetes.KUBE\_PING, KUBERNETES\_NAMESPACE, and KUBERNETES\_LABELS) and granting the default service account the view role on the namespace. For JBoss EAP 8, the clustering layer must be provisioned via Galleon during the build.

## Takeaways

- KUBE\_PING queries the Kubernetes API directly for pod IP addresses, then filters by namespace and labels to establish TCP connections.
- Configuring KUBE\_PING requires 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 permission errors.

## FAQ

### What is the difference between KUBE\_PING and DNS\_PING?

KUBE\_PING queries the Kubernetes API server for pod IP addresses, whereas DNS\_PING resolves pod IP addresses directly through DNS.

### Why does KUBE\_PING require namespace details?

The protocol queries pod IP addresses across the cluster, then uses the namespace and labels to filter which pods receive ping and join requests.

### What is required to configure KUBE\_PING in JBoss EAP 7 or 8?

Configuring kubernetes.KUBE\_PING requires service account permissions and 3 environment variables: JGROUPS\_PING\_PROTOCOL, KUBERNETES\_NAMESPACE, and KUBERNETES\_LABELS.

**Tags:** [Clustering](https://yomu.fyi/topic/clustering), [JBoss EAP](https://yomu.fyi/topic/jboss-eap), [JGroups](https://yomu.fyi/topic/jgroups), [KUBE\_PING](https://yomu.fyi/topic/kube-ping), [OpenShift](https://yomu.fyi/topic/openshift)

- Source: [Red Hat](https://developers.redhat.com/articles/2026/11/03/jboss-eap-clustering-openshift-kubeping-discovery)
- Source URL: https://developers.redhat.com/articles/2026/11/03/jboss-eap-clustering-openshift-kubeping-discovery
- Ingested by Yomu: 2026-11-03T15:00:16.773Z

[Read original post](https://developers.redhat.com/articles/2026/11/03/jboss-eap-clustering-openshift-kubeping-discovery)
