Configure Service Mesh

configure service mesh breadcrumb

To configure Anypoint Service Mesh, you must first provision the Anypoint Service Mesh adapter, create an API, and then bind the adapter to that API. Each adapter is bound to a specific namespace. Therefore, a namespace can be associated with only one adapter at any given time.

Every service that you want Anypoint Service Mesh to manage from your Kubernetes Cluster must have a corresponding API in Anypoint Platform. After you create the API, you must then bind the service in the cluster to the corresponding API in Anypoint Platform.

In Kubernetes, services are an abstraction on top of the applications running on a set of pods as a network service. You configure Anypoint Service Mesh using the following three steps:

  1. Provision Anypoint Service Mesh Adapter.

  2. Create an API.

  3. Bind your service.

Methods for Configuring Anypoint Service Mesh

You can configure Anypoint Service Mesh using the command line interface (CLI) or using the Kubernetes custom resource definition (CRD) based on your preference:

Configuring Response Headers for Anypoint Service Mesh

Services protected by Anypoint Service Mesh return extra headers. These headers are added by Envoy and the gRPC adapter. If you use an Ingress, you can remove these headers to avoid returning them to the client.

Envoy added headers include:

  • x-envoy-upstream-service-time

  • x-envoy-decorator-operation

The Mule adapter adds the x-mule-report header.

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub
Give us your feedback!
We want to build the best documentation experience for you!
Help us improve with your feedback.
Take the survey!