Does Istio multicluster service mesh support headless services?

#1

We have a database running in k8s.
It exposes headless services of the below form.
cluster.namespace.svc.cluster.local
node1.cluster.namespace.svc.cluster.local
node2.cluster.namespace.svc.cluster.local
node3.cluster.namespace.svc.cluster.local

node(x).cluster.namespace.svc.cluster.local

Would Gateway based multicluster setup work here, by using some wildcard based ServiceEntry? Otherwise can you recommends some way to set the tunnel (VPN sort) between two kubernetes pod network (RancherLab’s Submariner is in nascent stages ?

0 Likes

#2

Yes, I think for multi clusters, headless configuration should be similar as single cluster.
ServiceEntry is a must.

0 Likes

#3

Hi @hzxuzhonghu Does Istio multicluster service mesh support headless services?)

Does ServiceEntry supports wildcard entries under .spec.hosts section or I need to manually enter all the endpoints there?

0 Likes

#4
0 Likes