Routing table does not show any READ roles

I have a 3 node CORE only neo4j (4.0.2) cluster setup in Azure Kubernetes service. I want to use bolt+routing/neo4j for writing into the cluster from another pod within the same AKS. But I seem to be getting this error

raise RoutingProtocolError("No read servers returned from server %r" % (address,))

neobolt.routing.RoutingProtocolError: No read servers returned from server Address(host=, port=7687)

And my routing table does not show any READ roles:

+------------------------------------------------------------------------------------------------------------------------------------+
| ttl | servers |
+------------------------------------------------------------------------------------------------------------------------------------+
| 300 | [{addresses: ["0.0.0.0:7687"], role: "WRITE"}, {addresses: ["0.0.0.0:7687", "0.0.0.0:7687", "0.0.0.0:7687"], role: "ROUTE"}] |
+------------------------------------------------------------------------------------------------------------------------------------+

Can anyone please suggest what might be going wrong? I have tried explicitly setting this property

causal_clustering.cluster_allow_reads_on_followers=true

but that didnt help as well.

I was missing out to set the property dbms_connector_bolt_advertised__address.
It is working now.