Confluent SchemaRegistry throwing Leader not known Error

Hi, We have been using Schema Registry in HA mode with 3 replicas. We have started seeing Leader not known.

error intermittently. We have made leader.eligibility=true in the configuration.

All the 3 pods are running behind a ClusterIp-type service in a k8s cluster. We don’t see any other major error logs in the pods so it’s kind of hard to find the issue. Can you please help us if finding out the root cause of this?

I beleive it’s because they cannot communicate to each other and you need to set the advertised host name to the pod if when deployed.
Using Confluent’s container image I set

                  fieldPath: status.podIP

to achieve this.