Istio and Kubernetes are a common pairing in a modern DevOps stack. Here is how they fit together and a practical way to wire them up.
Where Istio fits
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.
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: 10Where Kubernetes fits
Kubernetes is a container orchestrator: you declare the desired state of your workloads in YAML and controllers continuously reconcile the cluster toward it, handling scheduling, scaling, healing and networking.
apiVersion: apps/v1
kind: Deployment
metadata: { name: web }
spec:
replicas: 3
selector: { matchLabels: { app: web } }
template:
metadata: { labels: { app: web } }
spec:
containers:
- name: web
image: ghcr.io/acme/web:1.0
ports: [{ containerPort: 3000 }]
resources:
requests: { cpu: 100m, memory: 128Mi }
limits: { cpu: 500m, memory: 256Mi }
readinessProbe:
httpGet: { path: /healthz, port: 3000 }
---
apiVersion: v1
kind: Service
metadata: { name: web }
spec:
selector: { app: web }
ports: [{ port: 80, targetPort: 3000 }]Making them work together
- Start with mTLS and telemetry; add traffic rules only when needed
- Use istioctl analyze in CI to catch misconfigurations
- Set requests/limits and use the HorizontalPodAutoscaler for elastic workloads
- Separate config (ConfigMap) from secrets and mount them, don't bake them in
Want this pairing set up properly, with docs and handover? That is exactly the kind of work CodeWizard's embedded senior engineers do - and both Istio and Kubernetes have active community groups you can join for free.