Esta página se muestra en inglés. Una traducción al español está en curso.
SkillsApr 11, 2026·3 min de lectura

Istio — Open Source Service Mesh for Microservices

Istio is the leading open-source service mesh. Connect, secure, control, and observe services with mTLS encryption, traffic management, and observability — all without changing application code.

AI Open Source
AI Open Source · Community
Listo para agents

Instalación con revisión previa

Este activo requiere revisión. El prompt copiado pide dry-run, muestra escrituras y continúa solo tras confirmación.

Needs Confirmation · 64/100Política: confirmar
Superficie agent
Cualquier agent MCP/CLI
Tipo
Skill
Instalación
Single
Confianza
Confianza: Established
Entrada
step-1.md
Comando con revisión previa
npx -y tokrepo@latest install e66c0370-3558-11f1-9bc6-00163e2b0d79 --target codex

Primero dry-run, confirma las escrituras y luego ejecuta este comando.

TL;DR
Istio provides mTLS, traffic management, and observability for microservices without changing application code.
§01

What it is

Istio is an open-source service mesh that provides a uniform way to connect, secure, control, and observe services in a microservices architecture. It works by injecting Envoy sidecar proxies alongside each service pod in Kubernetes.

Istio targets platform teams running microservices on Kubernetes who need mutual TLS encryption, traffic routing (canary deployments, A/B testing), and distributed tracing without modifying application code.

§02

How it saves time or tokens

Istio handles cross-cutting concerns (encryption, retry logic, circuit breaking, observability) at the infrastructure layer. Application developers do not need to implement mTLS, retry policies, or distributed tracing in their code. The service mesh handles it transparently via Envoy sidecars.

§03

How to use

  1. Install Istio on your Kubernetes cluster:
curl -L https://istio.io/downloadIstio | sh -
cd istio-*
export PATH=$PWD/bin:$PATH
istioctl install --set profile=demo -y
  1. Enable sidecar injection for your namespace:
kubectl label namespace default istio-injection=enabled
  1. Deploy your services normally. Istio automatically injects Envoy sidecars.
§04

Example

# VirtualService for canary deployment
apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
  name: my-service
spec:
  hosts:
    - my-service
  http:
    - route:
        - destination:
            host: my-service
            subset: v1
          weight: 90
        - destination:
            host: my-service
            subset: v2
          weight: 10
§05

Related on TokRepo

§06

Common pitfalls

  • Istio sidecar injection increases pod resource usage. Each sidecar consumes CPU and memory. Plan cluster capacity accordingly.
  • The learning curve is steep. Start with the demo profile for evaluation and graduate to production profiles after understanding the components.
  • Istio version upgrades require careful planning. Sidecar proxies must be restarted after control plane upgrades.

Preguntas frecuentes

What is a service mesh?+

A service mesh is an infrastructure layer that handles service-to-service communication. It provides features like encryption, load balancing, retries, circuit breaking, and observability through proxy sidecars, without requiring code changes.

Does Istio require Kubernetes?+

Istio is primarily designed for Kubernetes. While Istio technically supports VM workloads, the best-supported deployment model is on Kubernetes with automatic sidecar injection.

What is mTLS in Istio?+

Mutual TLS (mTLS) means both the client and server authenticate each other with certificates. Istio automates mTLS between all services in the mesh, encrypting all inter-service traffic without application changes.

How does Istio affect application performance?+

Istio adds latency through sidecar proxies (typically 1-5ms per hop). The Envoy proxies also consume CPU and memory. For most applications, the overhead is acceptable given the security and observability benefits.

Can Istio do canary deployments?+

Yes. Istio VirtualService resources let you split traffic between service versions by percentage. You can gradually shift traffic from v1 to v2 (e.g., 90/10, then 50/50, then 0/100) without changing DNS or load balancer config.

Referencias (3)
Relacionados en TokRepo
DevOps toolsSecurity toolsMonitoring tools

Discusión

Inicia sesión para unirte a la discusión.
Aún no hay comentarios. Sé el primero en compartir tus ideas.

Activos relacionados

Kiali — Service Mesh Observability Console for Istio

Kiali is the official observability console for the Istio service mesh, providing topology visualization, traffic flow analysis, configuration validation, and distributed tracing integration.

Skills
AI Open Source

Linkerd — The Lightest, Fastest Service Mesh for Kubernetes

Linkerd is a CNCF-graduated service mesh built on a purpose-built Rust proxy. It delivers mTLS, traffic management, and observability with a fraction of the resource cost of Istio — and sets up in minutes.

Skills
AI Open Source

Headscale — Open Source Self-Hosted Tailscale Control Server

Headscale is an open-source implementation of the Tailscale control server. Run your own private mesh VPN with WireGuard, no Tailscale subscription needed.

Skills
AI Open Source

Plane — Open-Source AI Project Management

Open-source Jira/Linear alternative with AI-powered pages. Issues, sprints, modules, roadmaps, and real-time analytics. Self-hostable via Docker. AGPL-3.0, 47,500+ stars.

Skills
AI Open Source
◈Inicio🔍Buscar👤Yo