Issues with running Solace Helm chart with Redundancy and TLS enabled.
Trying to figure out what reason this would not work. I am able to use the solace helm chart (https://github.com/SolaceProducts/pubsubplus-kubernetes-quickstart) to run solace in my GKE kubernetes cluster with tls enabled using my cert secret, however when I enable redundancy, 2 of the pods will not become ready. I was able to confirm that if I run redundancy on with tls disabled, all 3 pods startup correctly. The pods themselves dont seem to give too much in the way of an error message, Readiness probe failed: Fri Feb 4 20:12:11 UTC 2022 INFO: readiness_check.sh-Waiting for valid server status response, got:
As well as: startup-broker.sh-Waited 110 seconds, Management API not yet accessible
<returnInfo><errorInfo>management host is not responding</errorInfo></returnInfo>
from the container logs.
There's a number of warnings in my container logs but nothing that stands out.
Curious if anyone has had this issue before if there is additional setup that is needed to use HA mode with TLS.