I know dapr has support for service discovery built in but how does that work when deployed to kubernetes in a cross cluster setup? Can't seem to find example or docs.

CodePudding user response：

Dapr is completely platform and language-independent; it means that it can run on any platform, any Kubernetes deployment, in the cloud or on-premise, and even on IoT (Internet of Things) devices too.Dapr is focused on providing building blocks that make it easier for developers to build microservices, unlike a service mesh, which is focused on networking concerns.

for example - dev, QA teams want to use a cluster environment. These can be segregated via namespaces. Multi-tenancy is the ability to have multiple distinct namespaces within a single cluster. Quotas and policies can be applied for each namespace and this enables a simple solution to segregate tenants.

Multi-cluster environment is where there are many separate clusters that need to communicate. These clusters can exist in a flat network setup where every pod IP is reachable from every other pod. Setting up such clusters is beyond the scope of this proposal.

The intention of this proposal is to enable Dapr features like actor invocation , and service invocation to work seamlessly and in a cohesive manner in multi-cluster environments.Concept of cross clusters for implementing Gateways across clusters.

Refer this GIT LINK for more information