Replies: 5 comments
-
Istio is doing this automatically - K8S is using ServiceExport. IMO GAMMA should probably support at least those 2 modes - not sure if we want more granularity or alternatives. |
Beta Was this translation helpful? Give feedback.
-
To me this almost sounds like a 'federation' - how do two meshes participate with each other. Whether they share a higher level management plane or not. |
Beta Was this translation helpful? Give feedback.
-
FWIW, I think this is actually distinct from federation. If two clusters "join" (that name isn't great) the same Mesh resource, they are part of the same mesh for the purposes of routing. I'm not sold that we want to actually do this in GAMMA though |
Beta Was this translation helpful? Give feedback.
-
As a recent update, GEP-1748 is proposing the adoption of MCS API for routing to services on other clusters within a clusterset (a group of clusters which has an assumption of sameness) by specifying a This doesn't yet address how to route to off-cluster services outside the local clusterset, but I'm hoping this is a good starting point and we can eventually work to expand the MCS API to support "cross-clusterset" routing in the future. |
Beta Was this translation helpful? Give feedback.
-
I still see multiple methods for routing. |
Beta Was this translation helpful? Give feedback.
-
In Kuma we have the concept of making a single mesh across multiple clusters. I am curious if the multi-cluster mesh use case feels important to other implementations, and if so would that be valuable across different mesh implementations, e.g. for GAMMA something like a
Mesh
resource which you can decorate to connect to anotherMesh
resource that lives in another cluster, so as to "join" it? Just generally curious for thoughts.Beta Was this translation helpful? Give feedback.
All reactions