Using Multiple Adapters
Meshery is capable of running zero or more service mesh adapters. Without any service mesh adapters, some but not all of Meshery’s features will continue to function (e.g. performance testing of workloads not running on a service mesh).
Modifying the default adapter deployment configuration
The number of adapters, type of adapters, where they are deployed, how they are named and what port they are exposed on are all configurable deployment options. To modify the default configuration, find
~/.meshery/meshery.yaml on your system.
~/.meshery/meshery.yaml is a Docker Compose file.
Configuration: Running fewer Meshery adapters
To customize which Meshery Adapters are used in which deployments, customize your contexts in your meshconfig.
Configure your meshconfig, using
mesheryctl system context to customize which Meshery Adapters are used in which deployments.
Alternatively, directly modify youn the
~/.meshery/meshery.yaml configuration file, remove the entry(ies) of the adapter(s) you are removing from your deployment.
Configuration: Running more than one instance of the same Meshery adapter
The default configuration of a Meshery deployment includes one instance of each of the Meshery adapters (that have reached a stable version status). You may choose to run multiple instances of the same type of Meshery adapter; e.g. two instances of the Meshery Adapter for Istio. To do so, modify
~/.meshery/meshery.yaml to include multiple copies of the given adapter.
Demo of Meshery managing service mesh deployments across multiple clusters:
See on YouTube: Cloud Native Austin Virtual Meetup: April 2020