Simplify Istio service mesh configuration with production-ready templates for routing, canary deployments, circuit breakers, and traffic shifting. Eliminate trial-and-error with proven patterns.
Baixar o ZIP da skill
Upload no Claude
Vá em Configurações → Capacidades → Skills → Upload skill
Ative e comece a usar
Testar
A utilizar "istio-traffic-management". Create a canary deployment with 10% traffic
Resultado esperado:
Generates VirtualService with weight-based routing (90% stable, 10% canary) and DestinationRule defining both subsets with version labels
A utilizar "istio-traffic-management". Add retries and timeout to orders service
Resultado esperado:
Creates VirtualService with 3 retry attempts, 3s per-try timeout, and 10s overall timeout for the orders host
A utilizar "istio-traffic-management". Set up circuit breaker for checkout service
Resultado esperado:
Generates DestinationRule with connection pool limits and outlier detection including consecutive5xxErrors and baseEjectionTime
Auditoria de Segurança
SeguroAll static analysis findings are false positives. The skill contains only YAML configuration templates and documentation for Istio traffic management. The 'external commands' flagged are bash commands in markdown documentation blocks (istioctl commands). The 'weak cryptographic algorithm' warnings are triggered by Istio API version strings (v1beta1) in YAML headers, not actual crypto. The 'hardcoded URLs' are legitimate links to official Istio documentation. No executable code, no security risks, no prompt injection attempts detected.
Problemas de Baixo Risco (1)
Pontuação de qualidade
O Que Você Pode Construir
Platform Engineer Setting Up Canary Deployments
Configure gradual traffic rollout from stable to canary versions with weighted routing and automatic rollback on failures.
DevOps Engineer Implementing Resilience Patterns
Add circuit breakers, retries, and timeouts to prevent cascading failures and improve service reliability.
SRE Debugging Traffic Routing Issues
Use istioctl commands to analyze and validate VirtualService and DestinationRule configurations in production clusters.
Tente Estes Prompts
Create a VirtualService for my-service that routes traffic based on the x-user header. Send users with header value 'beta' to v2 subset, all others to v1.
Set up a canary deployment for payment-service. Route 95% of traffic to stable version, 5% to canary. Include DestinationRule with both subsets.
Create a DestinationRule for api-service with circuit breaker settings: max 100 connections, 1000 HTTP requests, eject pods after 5 consecutive errors, 30s base ejection time.
Set up traffic mirroring from production to staging. Mirror 100% of requests to v2 subset for testing without affecting live traffic.
Melhores Práticas
- Always test Istio configurations with istioctl analyze before applying to production
- Start with simple VirtualService rules and add complexity incrementally
- Monitor traffic patterns with Kiali dashboards after deploying new routing rules
- Use meaningful subset names (stable, canary, v1, v2) and label services consistently
Evitar
- Do not configure retries without limits - this can cause cascading failures
- Avoid mirroring traffic to production databases - mirror to test environments only
- Never skip subset validation in DestinationRules - undefined subsets cause routing failures
- Do not use 100% canary weight immediately - always start with small percentages
Perguntas Frequentes
What is the difference between VirtualService and DestinationRule?
How do I gradually increase canary traffic?
Why is my traffic not reaching the canary subset?
Can I use this skill without Istio installed?
How do I debug routing issues?
What is traffic mirroring used for?
Detalhes do Desenvolvedor
Autor
sickn33Licença
MIT
Repositório
https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/istio-traffic-managementReferência
main
Estrutura de arquivos
📄 SKILL.md