Currently kubernetes.KUBE_PING is the protocol in use when cloud is enabled.

KUBE_PING, although requiring an Openshift permission, is the simpler configuration wise (just need KUBERNETES namespace and your are done).

DNS_PING doesn't require the extra permission but requires a new service (to expose the port 8888 in the pod) to be created.

I propose that we keep KUBE_PING as the default protocol and extend the cloud element with a <ping-protocol>kubernetes.KUBE_PING|dns.DNS_PING</ping-protocol> element.

The env variable used to set the service name is the same as EAP/XP S2I builder image: OPENSHIFT_DNS_PING_SERVICE_NAME

web-clustering example will be evolved with a profile to support DNS_PING (and also to contain a yaml example file of the ping service).

kwills@redhat.com, mchoma@redhat.com, brian.stansberry fburzigo@redhat.com that is the proposal to also cover DNS_PING.