Service Mesh Interface (SMI) Standard
What you'll learn: How the SMI specification creates a common API layer across different service mesh implementations in Kubernetes.
The Service Mesh Standardization Problem
You've just explored multiple service mesh options: Istio, Linkerd, Consul, OSM, and Kuma. Each provides similar capabilities—traffic management, observability, security—but with completely different APIs and configuration formats. If you build applications tightly coupled to one mesh's API, switching providers becomes a major rewrite.
What is SMI?
Service Mesh Interface (SMI) is a specification that defines a standard set of Kubernetes Custom Resource Definitions (CRDs) for common service mesh functionality. Think of it as an abstraction layer—like how JDBC lets Java applications work with different databases through a common interface.
SMI provides vendor-neutral APIs for:
- Traffic specs - Define protocols and routes
- Traffic split - Weighted routing for canary deployments
- Traffic access control - Service-to-service authorization policies
- Traffic metrics - Standard telemetry collection
Why It Matters
With SMI, you write your traffic policies, access controls, and telemetry configurations once using standard SMI resources. Service mesh implementations like Linkerd, OSM, and Consul (with adapters) translate these SMI resources into their native formats.
This interoperability means:
- Portability: Switch meshes without rewriting policies
- Tool compatibility: Monitoring tools work across meshes
- Ecosystem growth: Third-party tools target one standard instead of many
The Reality Check
While SMI provides valuable standardization, it covers only a subset of mesh capabilities. Advanced features remain implementation-specific. Think of SMI as the "minimum viable API" for service mesh operations.
Key Takeaway: SMI provides a vendor-neutral standard API for basic service mesh operations in Kubernetes, enabling portability and interoperability across different mesh implementations while accepting that advanced features will remain mesh-specific.