← All insightsCheat Sheet

Istio cheat sheet: the complete command reference

CodeWizard Engineering · 11 March 2026 · 3 min read · Beginner

This is a complete, hands-on Istio cheat sheet: install, configure, operate, automate and secure it - with copy-paste commands grouped by task. Bookmark it for day-to-day work, incidents and interviews alike.

Istio is a service mesh that injects sidecar (or ambient) proxies to give you mutual TLS, fine-grained traffic routing, retries, and rich telemetry across services - configured with Kubernetes CRDs.

Why you reach for it

  • Automatic mTLS between services with zero app changes
  • Traffic shifting for canary and blue-green releases
  • Uniform metrics, logs and traces for all service-to-service calls

Installation

bash
istioctl install --set profile=demo -y
kubectl label namespace default istio-injection=enabled
istioctl verify-install

Configuration reference

Shift 10% of traffic to v2 with a VirtualService.

yaml
apiVersion: networking.istio.io/v1
kind: VirtualService
metadata: { name: web }
spec:
  hosts: [web]
  http:
    - route:
        - destination: { host: web, subset: v1 }
          weight: 90
        - destination: { host: web, subset: v2 }
          weight: 10

Core commands you use daily

bash
istioctl proxy-status
istioctl analyze
istioctl dashboard kiali

Install & inspect

bash
istioctl install --set profile=demo -y
istioctl analyze
istioctl proxy-status
istioctl proxy-config routes deploy/web
istioctl dashboard kiali

Inject & verify

bash
kubectl label namespace default istio-injection=enabled
istioctl kube-inject -f deploy.yaml | kubectl apply -f -
istioctl verify-install

Use it in CI/CD

Enforce strict mTLS mesh-wide.

yaml
apiVersion: security.istio.io/v1
kind: PeerAuthentication
metadata: { name: default, namespace: istio-system }
spec: { mtls: { mode: STRICT } }

Best-practice checklist

  • Start with mTLS and telemetry; add traffic rules only when needed
  • Use istioctl analyze in CI to catch misconfigurations
  • Consider ambient mode to cut sidecar overhead

Common pitfalls to avoid

  • Adopting a mesh before you actually need its features - it adds real complexity
  • Sidecar resource overhead on tiny clusters
  • Conflicting VirtualServices producing surprising routing

Security quick wins

  • Enforce STRICT mTLS and default-deny AuthorizationPolicies
  • Keep the control plane and proxies patched

Works well with

  • Kubernetes - Declarative orchestration for containers at scale - self-healing, rolling updates and service discovery.
  • linkerd
  • Prometheus - The de-facto standard for metrics - a pull-based time-series database with a powerful query language.
A cheat sheet is muscle memory on paper - keep it close until the commands live in your fingers.

Want senior help putting Istio to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult