Service mesh overview (Istio) template
How a service mesh works: sidecar proxies beside every pod, mTLS between services, and a control plane pushing config and certs.
Use this templateFree, opens in your browser. No sign-up.
What's on the board
- Data plane · namespace shop (sidecar injection on)
- Envoy sidecar proxy · Ingress gateway (Envoy) · frontend (Next.js) · orders service · payments service
- Pod: frontend
- Pod: orders (v1 90% · v2 10%)
- Pod: payments
- Traffic management
- Canary: VirtualService sends 10% to orders v2 · Retries: 3 tries, 2 s timeout · Circuit breaker: eject after 5 × 5xx
- Security
- PeerAuthentication: mTLS STRICT · Only orders may call payments (authz policy) · SPIFFE identity per service account
- Observability
- Request metrics → Prometheus · Distributed traces → Jaeger · Live service graph in Kiali
Also on the board
- Control plane (istiod): config, mTLS certificates, service discovery
How to use this template
- Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
- Double-click any box to change its text. Replace the examples with your own content.
- Link by dragging. Hover a box and drag one of its dots onto another box. The whole box is the target, and links stay attached when you move things.
- Sketch, then convert. Draw boxes and arrows with the pen, select the strokes and click Convert sketch: they become real boxes and links.
- Group by environment or region. Draw a frame (F) around a group of services; moving the frame moves everything inside it.
Good for
- service mesh
- istio
- kubernetes
- microservices
- envoy
- Design reviews and architecture decision meetings
- Runbooks and onboarding for on-call engineers
- Planning a migration or a cost-cutting pass
Related templates
Kubernetes cluster overview
Ingress, services, deployments and pods in a namespace, with config, storage, control plane and add-ons around them.
GitOps workflow (Argo CD)
Deploy by pull request: CI builds the image, a config-repo PR bumps the tag, and Argo CD syncs the cluster to match git.
AWS three-tier web app
A highly available web app on AWS: DNS and CDN, load balancer, auto-scaled app servers and Multi-AZ database in a VPC.
CI/CD pipeline with quality gates
From pull request to production: build, tests, security scans, staging, approval and canary release, with the gates in between.
Microservices with API gateway
Clients behind an API gateway, services that each own their database, and an event bus for asynchronous work.
Saga pattern (distributed transactions)
An orchestrated saga: local transactions across services, the compensating steps that undo them, and orchestration vs choreography.