istio-traffic-management
Configure Istio traffic management fast
Managing Istio traffic policies across services is complex and error prone. This skill provides ready templates and guidance for routing, canary rollouts, and resilience controls.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "istio-traffic-management". Set up a 95 5 canary for payments with stable and canary subsets
Expected outcome:
- VirtualService routes payments with 95 percent stable and 5 percent canary
- DestinationRule defines stable and canary subsets with version labels
- Notes on adjusting weights during the rollout
Using "istio-traffic-management". Configure circuit breakers for my-api with max connections and outlier detection
Expected outcome:
- DestinationRule sets connection pool limits and outlier detection thresholds
- Circuit breaker triggers after 5 consecutive 5xx errors
- Ejection removes unhealthy instances for 30 seconds base time
Using "istio-traffic-management". Add retries and timeouts to the ratings service VirtualService
Expected outcome:
- VirtualService includes 3 retry attempts with 3 second per-try timeout
- Timeout set to 10 seconds per request
- Retries trigger on connect-failure, refused-stream, unavailable, and cancelled
Security Audit
SafeThis skill contains only static documentation with YAML configuration templates for Istio traffic management. No executable code, data access, network communication, or file manipulation is present. The 57 static findings are all false positives caused by YAML field names being misinterpreted as cryptographic terms, code block markers being flagged as shell backticks, and hash values being flagged as weak algorithms.
Risk Factors
🌐 Network access (4)
⚙️ External commands (19)
Quality Score
What You Can Build
Standardize mesh routing
Generate consistent VirtualService and DestinationRule patterns for team services.
Harden service resilience
Define retries, timeouts, and circuit breakers to reduce cascading failures.
Run safe canaries
Create weighted splits for stable and canary versions during rollouts.
Try These Prompts
Create a VirtualService and DestinationRule for reviews with v1 and v2 subsets. Route header end-user jason to v2 and others to v1.
Generate Istio manifests for my-service with stable and canary subsets. Use 90 percent stable and 10 percent canary.
Provide a DestinationRule with connection pools and outlier detection for my-service. Add a VirtualService with retries and timeouts.
Create a Gateway for *.example.com with TLS and a VirtualService that routes /api/v1 to api-service on port 8080.
Best Practices
- Use clear version labels for subsets
- Set conservative timeouts and retry limits
- Start canaries with small traffic weights
Avoid
- Mirroring traffic to production targets
- Unlimited retries without backoff
- Skipping outlier detection on critical paths