Hi Tim,
Thanks for your reply, yes we have configured one job previously to kill
one pod when two are up. it's working now.
My deployment file is available here if anyone is interested.
https://github.com/imranrazakhan/K8S-HA-ActiveMQ/blob/main/activemq.yaml
Regards,
I assume there aren't any failures earlier in broker1's logs that might be
relevant?
>From those logs, it looks like Kubernetes is shutting down ActiveMQ rather
than ActiveMQ shutting itself down, based largely on the fact that there is
nothing that indicates that ActiveMQ initiated the shutdown.
I have deployed two statefulset replicas of ActiveMQ 5.15.13 as Network
Broker, but second POD activemq-1 is restarting after every 4m51s (I
removed readiness and liveness probes too), I enabled debug logs but could
not find any clue
**ActiveMQ-0:**
http://activemq.apache.org/schema/core";
