Subagent Directive: Subagent: Service Mesh Expert
Subagent Directive: Subagent: Service Mesh Expert is a verified SUBAGENT blueprint on Promptally in Specialized Subagents optimized for leading AI models. 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. Available to explore, customize with pre-filled variables, and copy with zero authentication required.
Created by @promptallyTechnical Specifications
| Specification | Value |
|---|---|
| Artifact type | SUBAGENT (Specialized Subagents) |
| Compatible engines | Universal / Model Agnostic |
| Input variables | None (pre-filled) |
| Approximate tokens | 431 |
| Source file | service-mesh-expert.agent.md |
| Access tier | Free public (MIT) |
Pre-Filled Template
# 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
How to use this subagent
- Review the pre-filled example and source files above.
- Copy the template or download
service-mesh-expert.agent.md, then use it in your model, IDE, or workflow tool. - Compare your result with the sample output when one is provided.
Frequently Asked Questions
How do I use Subagent Directive: Subagent: Service Mesh Expert?
Open the subagent on Promptally, review the pre-filled example, then copy the template or download service-mesh-expert.agent.md and paste it into your model, IDE or workflow tool. Subagent Directive: Subagent: Service Mesh Expert is a static blueprint with no dynamic variables. Copy it and use it as-is.
Is Subagent Directive: Subagent: Service Mesh Expert free?
Yes. Subagent Directive: Subagent: Service Mesh Expert is free to view, copy and download on Promptally without creating an account. It is published under the MIT license.
What variables does Subagent Directive: Subagent: Service Mesh Expert need?
Subagent Directive: Subagent: Service Mesh Expert is a static blueprint with no dynamic variables. Copy it and use it as-is.