Hello,
Someone form the clustering team may want to validate that but this is my thinking:
protocol is a resource not an attribute thus there is no notion of list.
So to define your stack I'm afraid you would have to remove the stack and recreate it (as the order has a meaning iirc).
Some yaml like this works:
subsystem:
jgroups:
stack:
tcpping:
transport:
TCP:
socket-binding: jgroups-tcp
protocol:
TCPPING:
socket-bindings:
- jgroups-site2-eap1
- jgroups-site1-eap1
- jgroups-site2-eap2
- jgroups-site1-eap2
properties:
initial_hosts: "10.0.4.20[7600],10.0.3.23[7600],10.0.4.30[7600],10.0.3.27[7600]"
port_range: 0
MERGE3:
FD_SOCK:
FD_ALL:
VERIFY_SUSPECT:
pbcast.NAKACK2:
UNICAST3:
pbcast.STABLE:
pbcast.GMS:
MFC:
FRAG3:
You can't add the index.
Maybe
wildfly-configuration:
subsystem:
jgroups:
stack:
tcpping:
protocol:
MPING: !remove
kubernetes.KUBE_PING:
add-index: 0
properties:
namespace: "expression '${env.KUBERNETES_NAMESPACE}'"
labels: "expression 'app=myapp,environment=${env.ENVIRONMENT}'"
can work but I'm not sure in if add-index is an attribute of just a parameter so you might get your KUBE_PING at the end of the stack
Emmanuel
> --
> You received this message because you are subscribed to the Google Groups "WildFly" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
wildfly+u...@googlegroups.com.
> To view this discussion visit
https://groups.google.com/d/msgid/wildfly/baae7e42-931d-4264-b7a4-c2af38a470ddn%40googlegroups.com
> <
https://groups.google.com/d/msgid/wildfly/baae7e42-931d-4264-b7a4-c2af38a470ddn%40googlegroups.com?utm_medium=email&utm_source=footer>.