Services cannot talk to mirrored services #14241
Unanswered
Egor-Watson
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, new to Linkerd so I need some extra explanations.
Currently, I am trying to set up 2 clusters that can talk to each other to run some experiments. The idea is given the sock-shop/ hotel reservation microservice apps to deploy half the services on one cluster and the other half on the other cluster. The current set up is I have 2 Ubuntu VMs running K3s. I’ve followed the tutorials and got east → west connection working (though repeating the same steps but from west to east and the connection does not work, complaining about ServiceAccounts, ClusterRoleBindings, Roles and RoleBindings). I export my services on east and west can see them. I can ping the services from west. However say I deploy the frontend service on west, it cannot communicate with the services in east. From the docs I would expect that linkerd in the background would route the frontend’s requests to east.
Any idea how to properly set this up so that the frontend in west can communicate with all services in east? (I get it that in a real scenario this probably makes no sense, however I need to be able to deploy different microservices on different clusters and ensure the app still works as a whole).
Thanks in advance. Any tips on a more robust set up are also appreciated as the current linking is very unstable and needs to be redone almost every time the host computer reboots.
Beta Was this translation helpful? Give feedback.
All reactions