Linkerd mc link service not mirrored with different name of namespace

[YaaSSDD]

I everybody

I have two namespace with different names and I followed the tutorial linkerd multi-cluster all steps are ok installation of linkerd and modules linkerd mc and linkerd viz, I also managed to establish a connection and mirror the desired service but with two namespace of the same name except that when I try to make my Mirror service appear in my target namespace which has a different name it does not work would you have a solution for me?
Thanks in advance

For more context I have the back of namespace-toto which must join the back of namespace titi in API MTLS

What works :
Cluster A: namespace-toto
Cluster B: namespace-toto

What doesn't work:
Cluster A: namespace-toto
Cluster B: namespace-titi

[kflynn]

@YaaSSDD, this is actually as designed.

People doing Kubernetes application design are accustomed to namespaces providing a certain degree of isolation: for example, it's common to give a team control over a namespace for development. Kubernetes itself doesn't define how this concept should extend across clusters (in fact, Kubernetes doesn't really define anything across clusters), but most everyone implementing multicluster - including Linkerd - has adopted the position that "namespace sameness" is a reasonable pattern. This is the idea that, within a group of clusters that are administered as a single multicluster group, namespaces with the same name are considered to be a single namespace that spans the multicluster group – and namespaces that don't have the same name are assumed to be intentionally isolated.

Linkerd's multicluster implementation is designed to allow Services to span clusters within their namespace; we don't have a way to mirror into a different namespace, since it breaks namespace sameness. You could, of course, mirror Service foo in namespace namespace-toto and then have a workload talk to foo.namespace-toto.svc.cluster.local or the like.

I'm going to go ahead and close this issue, but feel free to comment further on it!

[YaaSSDD]

@kflynn thanks for your explanation and feedback i appreciate it,

I'm currently also using namespace logic with the aim of isolating my stacks but I'd like to use linkerd to communicate in MTLS with the api (not just to communicate between namespaces) of another stack in addition to the internal MTLS between pods,

Indeed, after some research and having found that this was not the default setting in Linkerd, I found a workaround solution in the form of a manual Mirror service, but I wondered whether this was a good practice.