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.
Do not use this skill when
- The task is unrelated to service mesh expert
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
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
Use this skill when
- 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
- Assess current infrastructure and requirements
- Design mesh topology and traffic policies
- Implement security policies (mTLS, AuthorizationPolicy)
- Configure observability (metrics, traces, logs)
- Set up traffic management rules
- Test failover and resilience patterns
- 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
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: service-mesh-expert3description: Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh con4license: MIT5---67# Service Mesh Expert89Expert 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.1011## Do not use this skill when1213- The task is unrelated to service mesh expert14- You need a different domain or tool outside this scope1516## Instructions1718- Clarify goals, constraints, and required inputs.19- Apply relevant best practices and validate outcomes.20- Provide actionable steps and verification.21- If detailed examples are required, open `resources/implementation-playbook.md`.2223## Capabilities2425- Istio and Linkerd installation, configuration, and optimization26- Traffic management: routing, load balancing, circuit breaking, retries27- mTLS configuration and certificate management28- Service mesh observability with distributed tracing29- Multi-cluster and multi-cloud mesh federation30- Progressive delivery with canary and blue-green deployments31- Security policies and authorization rules3233## Use this skill when3435- Implementing service-to-service communication in Kubernetes36- Setting up zero-trust networking with mTLS37- Configuring traffic splitting for canary deployments38- Debugging service mesh connectivity issues39- Implementing rate limiting and circuit breakers40- Setting up cross-cluster service discovery4142## Workflow43441. Assess current infrastructure and requirements452. Design mesh topology and traffic policies463. Implement security policies (mTLS, AuthorizationPolicy)474. Configure observability (metrics, traces, logs)485. Set up traffic management rules496. Test failover and resilience patterns507. Document operational runbooks5152## Best Practices5354- Start with permissive mode, gradually enforce strict mTLS55- Use namespaces for policy isolation56- Implement circuit breakers before they're needed57- Monitor mesh overhead (latency, resource usage)58- Keep sidecar resources appropriately sized59- Use destination rules for consistent load balancing6061## Limitations62- Use this skill only when the task clearly matches the scope described above.63- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.64- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
nous-hermeshub