Introduction
Meshery acts as an opinionated control plane for the cloud-native stack. It treats each Kubernetes distribution, service mesh, and Helm chart as a first-class component that you compose visually and deploy declaratively across clusters.
What Meshery Does
- Designs infrastructure visually via a drag-and-drop canvas (Kanvas)
- Installs and configures Istio, Linkerd, Consul, Cilium, Kuma, and more
- Benchmarks service mesh performance with a reproducible harness
- Validates configuration against CNCF best-practice policies
- Manages multi-cluster deployments from a single console
Architecture Overview
Meshery Server (Go) fronts a pluggable adapter model where each mesh or component ships an adapter implementing a gRPC contract. State lives in PostgreSQL or an embedded BadgerDB. The React UI talks to the server via REST/GraphQL, and mesheryctl wraps the same APIs for CI use.
Self-Hosting & Configuration
mesheryctl system start --platform dockerfor local dev- Helm chart
meshery/mesheryfor Kubernetes installs - Toggle adapters per mesh with
mesheryctl system config - Integrate SSO via OIDC or GitHub for team setups
- Persist designs in MeshPlans (YAML) checked into Git
Key Features
- Unified catalog of 500+ cloud-native components
- Performance testing with fortio and wrk2 baked in
- Policy-as-code using OPA for design-time validation
- Designs export as kustomize or Helm for portability
- Supports both standalone and control-plane-free operation
Comparison with Similar Tools
- Rancher Fleet — GitOps focused, less mesh-aware
- Argo CD — app delivery, not infra modeling
- Crossplane — composes cloud resources, different scope
- KubeSphere — broader platform, less mesh benchmarking
- Istio Operator UI — single mesh, no multi-cluster
FAQ
Q: Is Meshery an alternative to Istio? A: No — it manages Istio (and others). You still pick the mesh.
Q: Does it require internet? A: For catalog sync; air-gapped installs can snapshot the catalog offline.
Q: Who governs it? A: CNCF sandbox project, led by Layer5.
Q: Can I use Meshery for non-mesh components? A: Yes — the component model covers any Kubernetes CRD or Helm chart.