| name | configuring-service-meshes |
| description | Configure this skill configures service meshes like istio and linkerd for microservices. it generates production-ready configurations, implements best practices, and ensures a security-first approach. use this skill when the user asks to "configure service ... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
|
| allowed-tools | Read, Write, Edit, Grep, Glob, Bash(cmd:*) |
| version | 1.0.0 |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| license | MIT |
| compatible-with | claude-code, codex, openclaw |
| tags | ["devops","security","microservices"] |
Configuring Service Meshes
Overview
Configure service meshes (Istio, Linkerd, Consul Connect) for Kubernetes microservices architectures. Generate mTLS configurations, traffic management rules (routing, splitting, mirroring), observability integrations (distributed tracing, metrics), and resilience patterns (retries, circuit breakers, timeouts).
Prerequisites
- Kubernetes cluster accessible via
kubectl with admin permissions
- Service mesh CLI installed:
istioctl, linkerd, or consul
- Helm 3+ for service mesh installation charts
- Understanding of microservice communication patterns and dependencies
- Observability backend available (Jaeger, Zipkin, or Prometheus/Grafana) for tracing and metrics
Instructions
- Select the service mesh based on requirements: Istio for full-featured L7 control, Linkerd for lightweight simplicity, Consul Connect for multi-platform
- Install the control plane:
istioctl install --set profile=production or linkerd install | kubectl apply -f -
- Enable sidecar injection for target namespaces: label namespaces with
istio-injection=enabled or linkerd.io/inject=enabled
- Configure mTLS: set PeerAuthentication to STRICT mode for zero-trust inter-service communication
- Define traffic management rules: VirtualService for routing, DestinationRule for load balancing and circuit breaking
- Set up traffic splitting for canary deployments: route a percentage of traffic to the new version
- Configure retry policies and timeouts to improve resilience against transient failures
- Integrate observability: connect to Jaeger/Zipkin for distributed tracing, Prometheus for metrics, and Kiali for visualization
- Validate the mesh: verify sidecar injection, mTLS status, and traffic routing with
istioctl analyze or linkerd check
Output
- Service mesh installation manifests or Helm values
- PeerAuthentication and AuthorizationPolicy manifests for mTLS and RBAC
- VirtualService and DestinationRule manifests for traffic management
- ServiceEntry manifests for external service access
- Observability integration configuration (Jaeger, Prometheus, Kiali)
Error Handling
