Istio Configuration Resources Overview
You'll learn: How Istio uses Kubernetes Custom Resource Definitions (CRDs) to declaratively configure your service mesh's traffic routing, security policies, and observability settings.
Configuration as Custom Resources
Rather than managing configuration files or calling APIs directly, Istio extends Kubernetes with its own set of Custom Resource Definitions (CRDs). These resources let you define how your service mesh should behave using familiar kubectl apply workflows, just like deploying pods or services.
Think of Istio's CRDs as specialized dials and switches for your mesh—each resource type controls a different aspect of service communication.
The Three Pillars of Istio Resources
Istio's configuration resources fall into three main categories:
Traffic Management
Resources like VirtualService, DestinationRule, and Gateway control how requests flow between services. These define routing rules, load balancing strategies, and traffic splitting for canary deployments.
Security
Resources such as PeerAuthentication and AuthorizationPolicy configure mutual TLS (mTLS) between services and define which services can communicate with each other. They enforce security boundaries without changing application code.
Observability
Resources like Telemetry configure what metrics, logs, and traces Istio collects from the Envoy proxies in your data plane, feeding monitoring systems with rich service-level insights.
Why Custom Resources?
This declarative approach means your mesh configuration lives in version control alongside your application manifests, can be reviewed through pull requests, and benefits from Kubernetes' reconciliation model—Istio continuously ensures reality matches your desired state.
Key Takeaway: Istio uses Kubernetes Custom Resources to declaratively configure all aspects of your service mesh, organizing them into traffic management, security, and observability categories that work together through the control plane's translation to Envoy proxy configurations.