Skip to main content
skill CX Codex

istio-expert — Claude Code skill: Istio setup

The istio-expert skill helps manage Istio traffic, mTLS, and observability in Kubernetes. Use it to inspect a mesh or work through access policies.

Apache-2.0 184 installs ★ 45 updated 2026-10-12

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add personamanagmentlayer/pcl --skill istio-expert -a claude-code
Open on GitHub

What istio-expert does

The skill covers Istio service mesh configuration in Kubernetes, including VirtualService routing, gateways, load balancing, circuit breaking, mTLS, and AuthorizationPolicy. It also points to istioctl and kubectl commands for checks such as analyzing configuration, inspecting proxy status, and viewing sidecar logs.

Its guidance recommends moving from PERMISSIVE to STRICT gradually, setting timeouts and health checks, and monitoring latency, traffic, errors, and resource use. Further architecture and configuration material lives in references/CORE_CONCEPTS.md and is read on demand.

The stated requirements are Istio 1.20 or later and Kubernetes 1.28 or later. Cluster checks rely on kubectl and istioctl, so those tools need to be available to run the suggested commands.

What it helps with

  • route requests with VirtualService
  • inspect Istio configuration and proxy status
  • move mTLS from PERMISSIVE toward STRICT
  • configure timeouts, retries, and circuit breaking
  • restrict service access with AuthorizationPolicy

Example prompts for the agent

  • Inspect my Kubernetes Istio setup and find routing issues in VirtualService.
  • Show a gradual plan for enforcing strict mTLS in the production namespace.
  • Use istioctl to check the mesh and suggest an AuthorizationPolicy for this service.

How to install istio-expert

1Skills CLI (Vercel)

npx skills add personamanagmentlayer/pcl --skill istio-expert -a claude-code

2Manually: put the files in place

~/.claude/skills/istio-expert/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/istio-expert/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about istio-expert

How do I install istio-expert in Claude Code?

Run npx skills add personamanagmentlayer/pcl --skill istio-expert -a claude-code. The skill file is at ~/.claude/skills/istio-expert/SKILL.md.

What does istio-expert do?

It assists with Istio routing, security, and observability for Kubernetes. It also guides mesh checks using istioctl and kubectl.

Which Istio and Kubernetes versions does it require?

The listed requirements are Istio 1.20 or later and Kubernetes 1.28 or later.

Source text

SKILL.md · Apache-2.0
---
name: istio-expert
version: 1.1.0
description: >-
  Expert-level Istio service mesh management, traffic control, security, and observability
  for Kubernetes. Use when the user mentions service mesh, Kubernetes, microservices, mTLS,
  or traffic management, or when the task involves Istio Architecture, VirtualService -
  Traffic Routing, Gateway - Ingress/Egress, or Security - mTLS and Authorization.
category: devops
author: PCL Team
license: Apache-2.0
tags:
  - istio
  - service-mesh
  - kubernetes
  - microservices
  - mtls
  - traffic-management
allowed-tools:
  - Read
  - Write
  - Edit
  - Bash(kubectl:*, istioctl:*)
  - Glob
  - Grep
requirements:
  istio: '>=1.20'
  kubernetes: '>=1.28'
---

# Istio Expert

You are an expert in Istio service mesh with deep knowledge of traffic management, security, observability, and production operations. You design and manage secure, observable microservices architectures using Istio's control plane and data plane.

## istioctl Commands

**Installation and Management:**

```bash
# Install Istio
istioctl install --set profile=demo -y
istioctl install --set profile=production -y

# Verify installation
istioctl verify-install

# Show mesh status
istioctl proxy-status

# Analyze configuration
istioctl analyze
istioctl analyze -n production

# Show Envoy config
istioctl proxy-config cluster <pod-name>
istioctl proxy-config listener <pod-name>
istioctl proxy-config route <pod-name>
istioctl proxy-config endpoint <pod-name>
```

**Debugging:**

```bash
# Check injection status
kubectl get namespace -L istio-injection

# Describe pod with sidecar
kubectl describe pod <pod-name>

# Get Envoy logs
kubectl logs <pod-name> -c istio-proxy

# Dashboard
istioctl dashboard kiali
istioctl dashboard prometheus
istioctl dashboard grafana
istioctl dashboard jaeger

# Profile application
istioctl experimental profile diff default production
```

## Best Practices

### 1. Start with Permissive mTLS

```yaml
# Gradually migrate to STRICT
spec:
  mtls:
    mode: PERMISSIVE # Start here
    # mode: STRICT    # Move to this
```

### 2. Use Namespace-Level Policies

```yaml
# Apply at namespace level for consistency
metadata:
  namespace: production
```

### 3. Set Timeouts and Retries

```yaml
http:
  - route:
      - destination:
          host: service
    timeout: 10s
    retries:
      attempts: 3
      perTryTimeout: 2s
```

### 4. Implement Circuit Breaking

```yaml
trafficPolicy:
  connectionPool:
    http:
      http1MaxPendingRequests: 10
  outlierDetection:
    consecutive5xxErrors: 5
    interval: 30s
```

### 5. Monitor Golden Metrics

```
- Latency (request duration)
- Traffic (requests per second)
- Errors (error rate)
- Saturation (resource usage)
```

## Anti-Patterns

**1. No Resource Limits:**

```yaml
# BAD: No sidecar resource limits
# GOOD: Set explicit limits
spec:
  template:
    metadata:
      annotations:
        sidecar.istio.io/proxyCPU: '100m'
        sidecar.istio.io/proxyMemory: '128Mi'
```

**2. Overly Permissive Policies:**

```yaml
# BAD: Allow all
action: ALLOW
rules:
- {}

# GOOD: Explicit rules
rules:
- from:
  - source:
      principals: ["cluster.local/ns/prod/sa/frontend"]
```

**3. No Health Checks:**

```yaml
# GOOD: Always define health checks
livenessProbe:
  httpGet:
    path: /health
readinessProbe:
  httpGet:
    path: /ready
```

## Approach

When implementing Istio:

1. **Start Small**: Enable for one namespace first
2. **Gradual Rollout**: Use PERMISSIVE mTLS before STRICT
3. **Monitor**: Set up observability before production
4. **Test**: Validate traffic routing in staging
5. **Security**: Implement zero-trust with AuthorizationPolicy
6. **Performance**: Tune connection pools and circuit breakers
7. **Documentation**: Document all VirtualServices and policies

Always design service mesh configurations that are secure, observable, and maintainable following cloud-native principles.

## Reference Documentation

Detailed material lives alongside this skill and is read on demand:

- [Core Expertise](references/CORE_CONCEPTS.md) — Istio Architecture, Installation, VirtualService - Traffic Routing, DestinationRule - Load Balancing & Circuit Breaking, Gateway - Ingress/Egress, Security - mTLS and Authorization, Observability - Telemetry

## Resources

- Istio Documentation: https://istio.io/latest/docs/
- Istio Best Practices: https://istio.io/latest/docs/ops/best-practices/
- Kiali Dashboard: https://kiali.io/
- Envoy Proxy: https://www.envoyproxy.io/

© PCL Team · Apache-2.0 · personamanagmentlayer/pcl

Similar skills

All skills for DevOps and infrastructure →
ai-inference-service-mesh devops-skills ai-inference-service-mesh — a skill for Claude Code, Codex, Cursor and other platforms that manages AI inference traffic through Istio or Linkerd: mTLS, canary releases, access policies and circuit breakers. CX Codex +1 344installs microservices-patterns manutej microservices-patterns — a microservices skill covering service mesh, circuit breakers, traffic splitting and Istio. Useful when services fail in cascades or you need a canary release. CX Codex +1 447installs service-mesh-expert Seth Hobson service-mesh-expert — an architect subagent for service mesh work: traffic routing, mTLS, multi-cluster setups in Kubernetes. Useful when Istio or Linkerd needs configuring without guesswork. CX Codex ★ 42,780repo stars linkerd-patterns Seth Hobson linkerd-patterns is a Claude Code skill for configuring Linkerd in Kubernetes, with patterns for mTLS, traffic policies, canary releases, and multi-cluster networking. CX Codex +1 10,200installs microservices-architect VoltAgent Community microservices-architect designs distributed architectures and breaks monoliths into independent microservices. Sets up communication patterns across services using gRPC, Kafka, and service meshes. CX Codex 376installs microservices-architecture aj-geddes microservices-architecture guides AI coding assistants through microservice design, service boundaries, and distributed messaging. Helps break apart monoliths into isolated services. CX Codex +1 530installs

From the same set104

The whole set →
audit-expert audit-expert guides code security reviews, vulnerability checks, and compliance audits for SOC 2, GDPR, HIPAA, and PCI-DSS. CX Codex +1 188installs typescript-expert typescript-expert — a skill for expert-level TypeScript 5.0+ development with strict typing, modern build tools, and testing frameworks. CX Codex +1 187installs ai-architect-expert ai-architect-expert — a skill for AI system design: training pipelines, feature stores, model registries and serving with metrics. Useful when a prototype outgrows the notebook. CX Codex +1 185installs qa-expert qa-expert — a skill for test automation, QA strategy, and defect management across Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode. CX Codex +1 184installs grpc-expert grpc-expert walks the agent through gRPC work: protobuf schemas, the four RPC styles, status codes, and the operational pieces such as load balancing and health checks. CX Codex +1 182installs media-expert media-expert — a skill for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode that gives the agent deep knowledge of media production, streaming, and broadcasting. CX Codex +1 182installs microservices-expert microservices-expert — a skill for microservices architecture, service communication, and distributed workflows. Use it when a task involves service mesh, failure handling, or system design. CX Codex +1 181installs api-design-expert api-design-expert walks your agent through HTTP API design: REST resources, GraphQL against gRPC, versioning schemes, one error shape. Handy before the first endpoint gets written. CX Codex +1 180installs

Project sponsors

Companies that keep this analytics open