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.
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
Example
User request:
Implement service-to-service communication in Kubernetes.
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 con"4risk: safe5source: community6date_added: "2026-02-27"7metadata:8 source: https://skillmd.com/skills/iradoweck/service-mesh-expert9---1011# Service Mesh Expert1213Expert 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.1415## Do not use this skill when1617- The task is unrelated to service mesh expert18- You need a different domain or tool outside this scope1920## Instructions2122- Clarify goals, constraints, and required inputs.23- Apply relevant best practices and validate outcomes.24- Provide actionable steps and verification.2526## Capabilities2728- Istio and Linkerd installation, configuration, and optimization29- Traffic management: routing, load balancing, circuit breaking, retries30- mTLS configuration and certificate management31- Service mesh observability with distributed tracing32- Multi-cluster and multi-cloud mesh federation33- Progressive delivery with canary and blue-green deployments34- Security policies and authorization rules3536## Use this skill when3738- Implementing service-to-service communication in Kubernetes39- Setting up zero-trust networking with mTLS40- Configuring traffic splitting for canary deployments41- Debugging service mesh connectivity issues42- Implementing rate limiting and circuit breakers43- Setting up cross-cluster service discovery4445## Workflow46471. Assess current infrastructure and requirements482. Design mesh topology and traffic policies493. Implement security policies (mTLS, AuthorizationPolicy)504. Configure observability (metrics, traces, logs)515. Set up traffic management rules526. Test failover and resilience patterns537. Document operational runbooks5455## Best Practices5657- Start with permissive mode, gradually enforce strict mTLS58- Use namespaces for policy isolation59- Implement circuit breakers before they're needed60- Monitor mesh overhead (latency, resource usage)61- Keep sidecar resources appropriately sized62- Use destination rules for consistent load balancing6364## Example6566**User request:**6768> Implement service-to-service communication in Kubernetes.6970## Limitations71- Use this skill only when the task clearly matches the scope described above.72- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.73- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.