---
title: "Service mesh expert: review, role & definition · Undominated.ai"
canonical: https://undominated.ai/agents/wshobson-service-mesh-expert/
description: "Treats a mesh change as traffic, security and observability, not as a sidecar install."
---

# Service mesh expert: review, role & definition · Undominated.ai

> Treats a mesh change as traffic, security and observability, not as a sidecar install.

[← Explore all agents](/agents/)

INFRASTRUCTURE AND DELIVERY / Seth Hobson

# Service mesh expert

Treats a mesh change as traffic, security and observability, not as a sidecar install.

 [Use this definition ↓](#setup)[Original source ↗](https://github.com/wshobson/agents/tree/46891e7e60da0e52baf1050b7b6391b64e84c6d9/plugins/cloud-infrastructure/agents)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 2 linked sources
 Publisher Seth Hobson
 Licence [MIT ↗](https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/LICENSE)
 Revision 46891e7e60da
 [Read what was—and wasn’t—checked ↓](#review)

“Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh configurations. …”

 [Seth Hobson · upstream description ↗](https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/plugins/cloud-infrastructure/agents/service-mesh-expert.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - The workflow orders topology, mTLS and authorization, observability, traffic rules, failover tests, and runbooks.
- Best practices say to start in permissive mode and only then enforce strict mTLS.

### A good fit for

 - Reviewing an Istio or Linkerd change as traffic policy plus observability.
- Requiring a failover test before treating a mesh rule as done.
- Supply the mesh implementation, cluster topology and authorized traffic/security changes.
- Produce topology, traffic-policy and resilience-test plans with operational runbooks.

### Weigh up before choosing

 - Frontmatter sets model to opus and does not declare tools or install Istio or Linkerd.
- The file is a Claude agent definition and does not install itself into a host.
- This review did not run the agent.
- The recommendation to start permissive is a migration heuristic, not permission to weaken an existing strict mTLS deployment; Istio and Linkerd APIs must not be mixed.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - plugins/cloud-infrastructure/agents/service-mesh-expert.md
- LICENSE
- Round 2: pinned definition, output contract and permission/dependency boundaries reread on 2026-10-14

### Our findings

 - Frontmatter name is service-mesh-expert and model is opus, with no tools key.
- Capabilities name Istio and Linkerd, plus mTLS, traffic splitting, and multi-cluster federation.
- The workflow includes implementing AuthorizationPolicy, configuring traces, and testing failover.
- Best practices say to start with permissive mode and gradually enforce strict mTLS.
- Its workflow includes metrics, traces and logs before testing failover and documenting operations.
- It explicitly asks to monitor mesh latency/resource overhead and size sidecar resources, so mesh adoption is not assumed to be free.

### Not established by this review

 - The agent was not executed against a live repository or host.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Use the role in your project.

[Upstream setup instructions ↗](https://code.claude.com/docs/en/sub-agents.md)
 - Download the original service-mesh-expert.md with its licence and attribution; inspect it before use.
- Place a working copy at .claude/agents/service-mesh-expert.md and delegate a bounded task by its frontmatter name, or install its upstream plugin (plugins/cloud-infrastructure) through the wshobson/agents marketplace as the README describes.
- Name the mesh and version actually installed and the namespaces in scope.
- Review any policy before it reaches a cluster, and test failover as the workflow’s step 6 asks.

### Before you start

 - Claude Code with project-agent support
- The current mesh topology, mesh product and version

### Compatibility

Claude Code subagents

### Implementation

Markdown

### Local role instructions

 - No tool allowlist is declared.

### Cost model

MIT. The file sets model to opus and does not state a price.

THE COMPLETE REVIEWED DEFINITION

## Read it before you reuse it.

Original source bytes, with attribution. Review the host-specific setup notes above.

 Copy definition ↗ [Download definition + licence ↗](/resources/agents/wshobson-service-mesh-expert/bundle.zip)[Raw Markdown ↗](/resources/agents/wshobson-service-mesh-expert/definition.md)
 ---
name: service-mesh-expert
description: Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh configurations. Use PROACTIVELY for service mesh architecture, zero-trust networking, or microservices communication patterns.
model: opus
---

# Service Mesh Expert

Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh configurations. Use PROACTIVELY for service mesh architecture, zero-trust networking, or microservices communication patterns.

## Capabilities

- Istio and Linkerd installation, configuration, and optimization
- Traffic management: routing, load balancing, circuit breaking, retries
- mTLS configuration and certificate management
- Service mesh observability with distributed tracing
- Multi-cluster and multi-cloud mesh federation
- Progressive delivery with canary and blue-green deployments
- Security policies and authorization rules

## When to Use

- Implementing service-to-service communication in Kubernetes
- Setting up zero-trust networking with mTLS
- Configuring traffic splitting for canary deployments
- Debugging service mesh connectivity issues
- Implementing rate limiting and circuit breakers
- Setting up cross-cluster service discovery

## Workflow

1. Assess current infrastructure and requirements
2. Design mesh topology and traffic policies
3. Implement security policies (mTLS, AuthorizationPolicy)
4. Configure observability (metrics, traces, logs)
5. Set up traffic management rules
6. Test failover and resilience patterns
7. Document operational runbooks

## Best Practices

- Start with permissive mode, gradually enforce strict mTLS
- Use namespaces for policy isolation
- Implement circuit breakers before they're needed
- Monitor mesh overhead (latency, resource usage)
- Keep sidecar resources appropriately sized
- Use destination rules for consistent load balancing

The download contains service-mesh-expert.md . Keep its filename when placing it in the agent directory described above.

By **Seth Hobson**. [Exact upstream source ↗](https://raw.githubusercontent.com/wshobson/agents/46891e7e60da0e52baf1050b7b6391b64e84c6d9/plugins/cloud-infrastructure/agents/service-mesh-expert.md) · [Licence](/resources/agents/wshobson-service-mesh-expert/LICENSE.txt) · [Attribution](/resources/agents/wshobson-service-mesh-expert/ATTRIBUTION.txt)

SHA-256 e0772d0a32dddf41d06c06216c7cefdfc4f3357601f01e3bd6c50c4a18a3faa2

 Read the applicable licence MIT License

Copyright (c) 2024 Seth Hobson

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Agent profile ↗](https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/plugins/cloud-infrastructure/agents/service-mesh-expert.md) Checked 2026-10-14 https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/plugins/cloud-infrastructure/agents/service-mesh-expert.md Supports: Role and stated limits
- [Repository licence ↗](https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/LICENSE) Checked 2026-10-14 https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/LICENSE Supports: Redistribution terms

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Bicep Planning ↗ Writes Azure Bicep implementation plans as deterministic, machine-readable Markdown under a write-scope guardrail — only .bicep-planning-files/ — grounding every resource in Microsoft docs and pinning Azure Verified Module versions from their changelogs.](/agents/github-bicep-plan/)[### Deploy with Verification ↗ Refuses to say shipped until the live system confirms the new revision.](/agents/wshobson-deploy-with-verification/)[### Docker Expert ↗ Reviews and rebuilds Dockerfiles for production — multi-stage builds, layer caching, non-root execution, distroless bases — and pairs image optimization with supply-chain hardening: SBOMs, cosign signing, SLSA provenance and CIS benchmark compliance.](/agents/voltagent-docker-expert/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Find reusable instructions](/skills/)
- [Inspect connections](/mcp-servers/)
- [Build a toolkit](/tools/)
- [Choose the model](/compare/)
