JBoss EAP 7 container images deploy on OpenShift with clustering enabled by default, using KUBE_PING to establish peer-to-peer TCP connections across matching pods. To function properly, the mechanism queries the Kubernetes API directly, requiring administrators to grant the deployment service account permission to view pods in the namespace. Releases have transitioned from openshift.KUBE_PING to kubernetes.KUBE_PING starting in version 7.4. Modifying discovery variables isolates pods, but completely disabling clustering requires editing standalone-openshift.xml in JBoss EAP 7 or excluding the clustering layer during Galleon provisioning in JBoss EAP 8.
Key points
Protocol naming conventions shifted starting in JBoss EAP 7.4 with kubernetes.KUBE_PING r…: Protocol naming conventions shifted starting in JBoss EAP 7.4 with kubernetes.KUBE_PING replacing openshift.KUBE_PING.
Altering discovery environment variables such as the namespace isolates pods but does not…: Altering discovery environment variables such as the namespace isolates pods but does not remove clustering features.
Fully eliminating clustering requires modifying configuration files in JBoss EAP 7 or exc…: Fully eliminating clustering requires modifying configuration files in JBoss EAP 7 or excluding Galleon layers in JBoss EAP 8.
Sources checked by our analysis pipeline: 1
This is part of a 2-part blog series about clustering in Red Hat JBoss Enterprise Application Platform (JBoss EAP) 7 and JBoss EAP 8 in Red Hat OpenShift 4. In the 1st part of this series, we examined how to configure DNS_PING for JBoss EAP on OpenShift.
In part 2, we explore the JGroups KUBE_PING
discovery protocol, examine how it queries the Kubernetes API directly, compare setup differences between JBoss EAP 7 and JBoss EAP 8, and troubleshoot common permissions and syntax pitfalls.
JBoss EAP clustering in OpenShift: KUBE_PING discovery
When JBoss EAP 7 is deployed in Red Hat OpenShift Container Platform, the JBoss EAP 7 image has clustering capabilities enabled by default. To enable clustering, JBoss EAP 7 relies on JGroups discovery protocols (also known as ping protocols), such as DNS_PING
or KUBE_PING
, to connect pods.
The 1st article described how to enable DNS_PING
, which is not enabled by default on the JBoss EAP 7 image and must be configured manually or built from a template. It drew from knowledge in EAP 7 DNS_PING tracing logs in…
Scrutiny is mounting over the deployment of face-scanning tools across high-profile entertainment properties following reports detailing how patrons are tracked and categorized. The issue has prompted backing for local legislative measures that would prohibit the collection of biometric information in public areas throughout the city. This push aims to address ongoing privacy and civil liberty concerns stemming from corporate surveillance practices.
Grocery retailers across the continent are prioritizing critical infrastructure defense to prevent future disruptions to their operations. The response follows a coordinated cyber incident that directly compromised temperature-control systems across multiple facilities. Technical teams are currently focused on fortifying connected cooling networks against additional unauthorized tampering.
Digital asset security faces severe challenges from sophisticated social engineering efforts targeted at unsuspecting professionals. Cryptocurrency exchange Binance disclosed the findings, revealing how attackers leveraged trusted professional platforms and commercial outreach to compromise their targets. The operation highlights the extensive reach and massive financial toll inflicted by state-sponsored cyber operations on the digital finance ecosystem.