Contextual routing configuration and service naming for multi-cluster service mesh

A system for adapting a contextual routing configuration, comprising:

• a first cluster, a second cluster, a third cluster, and a fourth cluster comprising a computer processor and memory,
• wherein the fourth cluster is configured to store:
• a first dependency of a first calling service on a called service, and
• a second dependency of a second calling service on the called service,
• wherein the first calling service is located in the first cluster,
• wherein the called service is located in the second cluster, and
• wherein the second calling service is located in the third cluster;
• and
• a contextual configuration manager executing on the fourth cluster and configured to:
• obtain the first dependency and the second dependency,
• generate, using the first dependency, a first contextual routing configuration for the first calling service that maps a name of the called service to an ingress point of the second cluster,
• generate, using the second dependency, a second contextual routing configuration for the second calling service that maps the name of the called service to the ingress point of the second cluster,
• detect a relocation of the called service to the third cluster,
• modify, after the relocation is detected, the first contextual routing configuration to map the name of the called service to an ingress point of the third cluster, thereby obtaining a modified first contextual routing configuration by, and
• modify, after the relocation is detected, the second contextual routing configuration to map the name of the called service to a local name of the called service within a namespace of the third cluster, thereby obtaining a modified second contextual routing configuration.

A non-transitory computer readable medium comprising instructions that, when executed by a computer processor, perform:

• obtaining a first dependency of a first calling service on a called service and a second dependency of a second calling service on the called service,
• wherein the first calling service is hosted in a first cluster,
• wherein the called service is hosted in a second cluster, and
• wherein the second calling service is hosted in a third cluster;
• generating, using the first dependency, a first contextual routing configuration for the first calling service that maps a name of the called service to an ingress point of the second cluster;
• generating, using the second dependency, a second contextual routing configuration for the second calling service that maps the name of the called service to the ingress point of the second cluster;
• detecting a relocation of the called service to the third cluster;
• modifying, after detecting the relocation, the first contextual routing configuration to map the name of the called service to an ingress point of the third cluster, thereby obtaining a modified first contextual routing configuration;
• and
• modifying, after detecting the relocation, the second contextual routing configuration to map the name of the called service to a local name of the called service within a namespace of the third cluster, thereby obtaining a modified second contextual routing configuration.